On Sat, Jul 02, 2016 at 01:29:35PM -0400, Karl Dahlke wrote: > > What do we do in the first case, i.e. if we get ? > > When tidy sees it says "discarding unknown tag". > This may prove to be an unacceptable behavior at some point. > A lot depends on what other browsers do with it, > and whether we are expected to do the same. But these aren't unknown tags in tidy since they're html5, they're just unknown in Edbrowse. I'm wondering if there's anything we can do in the meantime whilst we get our html5 support completed to at least provide the html5 stuff as part of the DOM for use by js. Any ideas? I think that header, footer (probably comment and fragment too) should be treated like div in edbrowse, and probably same for article (and it's subtags) but obviously js needs to see the original element types. From memory there are a few more div-like tags as well though I can't remember what they are without going through the spec.