HTML 5 and the W3C, Going to Hell in a Handbasket

Image for post
Image for post
W3C, this X’er has two words for ya!

Problem #1, Nothing To Track Versions?

Problem #2, Documentative, not Authoritative

Problem #3, Except When It Is Authoritative

Example #1, <tbody> and <tfoot>

Example #2, “projection” and “tv” Media Targets

Example #3, <meta name=”x-ua-compatible”>

Image for post
Image for post
<meta
http-equiv="X-UA-Compatible"
content="IE=9"
>
<!--[if !IE]>-->
<link
rel="stylesheet"
href="templates/default/screen.css"
media="screen,projection,tv"
>
<!--<![endif]-->

Example #4, <SECTION> Needs a Numbered Heading?

So Basically….

Problem #4, It’s Not For “Us”

The HTML specification is not written for people who write HTML.

<div></div>

You shouldn’t have to go to an entirely separate document from the one defining the language, just to find out how to use tags like H1..H6 properly!

Problem #5, Undoing Decades of Progress

Problem #6, Validation Tools Become Meaningless

Image for post
Image for post
Not the kiddie table again Clark…

Conclusion

Written by

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store