This error correction is no reason to churn out invalid code, though. The
DOM that HTML5 creates for you might not be the DOM you want, so
ensuring that your HTML5 validates is still essential. With all this new stuff,
overlooking a small syntax error that stops your script from working or that
makes your CSS unstylish is easy, which is why we have HTML5 validators.
Far from legitimizing tag soup, HTML5 consigns it to history. Souper.
“I Need to Convert My XHTML Website to HTML5”
Is HTML5′s tolerance of looser syntax the death knell for XHTML? After all,
the working group to develop XHTML 2 was disbanded, right?
True, the XHTML 2 group was disbanded at the end of 2009; it was working
on an unimplemented spec that competed with HTML5, so having two
groups was a waste of W3C resources. But XHTML 1 was a finished spec
that is widely supported in all browsers and that will continue to work in
browsers for as long as needed. Your XHTML websites are therefore safe.
HTML5 Kills XML
Not at all. If you need to use XML rather than HTML, you can use XHTML5,
which includes all the wonders of HTML5 but which must be in well-formed
XHTML syntax (i.e. quoted attributes, trailing slashes to close some
elements, lowercase elements and the like.)
Actually, you can’t use all the wonders of HTML5 in XHTML5: