Linked by snydeq on Tue 16th Aug 2011 16:46 UTC
Web 2.0 InfoWorld's Peter Wayner discusses the 11 hard truths Web developers must accept in making the most of HTML5 -- especially those who are looking to leverage HTML5 in hopes of unseating native apps. 'The truth is, despite its powerful capabilities, HTML5 isn't the solution for every problem. Its additional features are compelling and will help make Web apps formidable competitors for native apps, but security issues, limitations of local data storage, synchonization challenges, and politics should have us all scaling back our expectations for the spec.'
Permalink for comment 485697
To read all comments associated with this story, please click here.
galvanash
Member since:
2006-01-25

You are completely missing my point...

If you author a document (say a white paper), you want to use document semantics. The new grouping tags (header, footer, article, etc.) are NOT document semantics - they are web page semantics.

It is to facilitate the very common practice of embedding a document that was created for stand-alone use into another document that was created to house web content... If the author of the original document did his job right, and you do your job right and use the new semantic grouping tags - you won't step on each other's toes so to speak.

The point is - if you do what a lot of people have done in the past (including me) and styled your H1 so that it behaves as a block header with a background image and other such stylistic stuff (not using ids or classes)... Well when you inject a document that contains H1 elements it all goes wonky. Sure, you can work around it about 20 different ways, but this avoids the whole problem quite elegantly imo.

I get where you are coming from - I really do. I also do not like wasting tags when they are not needed. But header, footer, nav, article, and aside are genuinely useful if you accept them for what they are - semantics created to match how people actually write web pages (as opposed to semantics for documents - which is what we had already). But whatever, to each his/her own. I don't expect to convince you to change your mind - but I hope I gave a rational enough argument that you at least won't continue thinking all people supporting HTML5 are stupid ;)

ps. The news sidebar on this site is a perfect example of what an aside is supposed to be. It IS related (it acts as an overflow to the main news items) but it is not critical (or integral) to it. I don't have a clue why you would think otherwise.

ps.ps. HTML5 supports ARIA roles just fine. But ARIA is not intended to be purely semantics - it is semantics with a concrete purpose (accessibility) and as such it is much more complex than the modest addition of a few tags. Its also still a draft spec and virtually no one is using it. Just saying...

Reply Parent Score: 2