Linked by Thom Holwerda on Wed 27th Feb 2013 01:59 UTC
Permalink for comment 553823
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 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2010-09-23
No, the point is that all modern browsers are rendering that page with broken code badly, but that IE has a compatibility view that allows it to be viewed "as it was tested to work in the past". This compatibility view is the reason that IE is better at running broken code.
And if you think that HTML5 will still be there 10 to 20 years from now you should look back at HTML 10 to 20 years ago and see how well that is still working.