Linked by snydeq on Tue 16th Aug 2011 16:46 UTC
Permalink for comment 485427
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2007-09-22
(I will try not to repeat what galvanash already mentioned)
Actually one of the big improvements in HTML5 is that many differences between how browsers parse (mistakes in) HTML should now be handled in the same way.
The scary part was that the W3C wanted to make an INcompatible XML-based version of (X)HTML following after (X)HTML4.
That would mean if you would visit a webpage with an older browser you wouldn't see anything useful.
No browser vendor wanted that, so that is one of the many reasons HTML5 or anything really came out of W3C for a long time.
Instead Mozilla and Opera started WHATWG to fix that, later Apple and, in a way, Google joined them.
The semantic elements exist to make it possible to create alternative layouts easier and to make it possible for other tooling to understand the page. Things like screen readers for blind people.
Some thing actually help reduce the foot print of pages.
That is also one of the reasons we now have a lot of new INPUT-tag-types. To not need extra JavaScript to handle what could easily be handled by the browser. Form validation and so on.
Even if you dislike that other people do add divs with 'nav' and 'header' to their page. Many are doing so. You'll have to agree that having a standard way of doing that can only be an improvement.