To view parent comment, click here.
To read all comments associated with this story, please click here.
Nobody is ever going to change the doctype in that page and that was the point in that post. This is not about how browsers handle new broken HTML5 code, it is about how browsers handle ANCIENT broken code.
For that IE has a compatibility view that works very nice and that makes IE a great browser for viewing broken code
My point was: different broken code will render differently in different browsers and versions.
This means this broken page renders fine in IE, other broken pages render fine in Chrome or Firefox.
And for new pages (HTML5) this should not be a problem anymore. Till will look the same in HTML5-browsers now as they will look the same in HTML-browsers in 10 or even 20 years.
This is also the same the person making the page will see it now when creating the HTML5-page.
Edited 2013-02-27 14:36 UTC





Member since:
2007-09-22
No, you are mistaken.
Broken HTML is rendered differently by different browser (versions).
But HTML5 does specify how HTML5 should be parsed and how broken HTML5 should be handled.
So if someone changes the 'doctype' in that page to a HTML5-doctype then all HTML5 browsers should render it the same.
The advantage of that is that if someone makes mistakes creating a HTML5-page and only checks it with one browser and likes what he/she seems then the result will be the same in all HTML5-browsers.