2 ms·

How much of this stuff will doom you if any of your users are still stuck on IE? (unclosed tags, new more concise doctypes, simpler document structure, utf8 ele

How much of this stuff will doom you if any of your users are still stuck on IE? (unclosed tags, new more concise doctypes, simpler document structure, utf8 element values and text, other cool HTML5 standard markup) Is this a preview of the web we might be able to write in fifteen years when Microsoft allows us to catch up?

yonran 15y ago
If your question is whether HTML5 is backward-compatible with IE6, then the answer is yes (as much as possible). It should be noted that much of the parsing complexity and looser validation are simply observations from IE6's behavior. The new elements and attributes are mostly just ignored in IE6 (article, input type=url, etc.) As for unclosed tags and unquoted attributes, they have been around since HTML 1.0[1], so I don't think you can blame HTML5 for introducing them. [1]: http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html http://www.w3.org/History/19921103-hypertext/hypertext/WWW/M...
sixtofour 15y ago
"How much of this stuff will doom you if any of your users are still stuck on IE?" Or "stuck" on Firefox. His nice minimal html running example works on Chromium/Ubuntu for me, but not on FF8/Ubuntu for me. In the part where you're supposed to see the html inside the pre tag, all I get rendered is "undefined", although I do get the three emphasized bangs at the end of "Foundation." Is this all "nice if you're on Chrom(ium)", or am I likely doing it wrong?