Linked by Thom Holwerda on Wed 27th Feb 2013 01:59 UTC
Internet Explorer "Internet Explorer 10 is available worldwide in 95 languages for download today. We will begin auto updating Windows 7 customers to IE10 in the weeks ahead, starting today with customers running the IE10 Release Preview. With this final release, IE10 brings the same leading standards support, with improved performance, security, privacy, reliability that consumers enjoy on Windows 8, to Windows 7 customers."
Thread beginning with comment 553817
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: That's cool.
by Lennie on Wed 27th Feb 2013 14:34 UTC in reply to "RE[2]: That's cool."
Lennie
Member since:
2007-09-22

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

Reply Parent Score: 2

RE[4]: That's cool.
by avgalen on Wed 27th Feb 2013 15:55 in reply to "RE[3]: That's cool."
avgalen 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.

Reply Parent Score: 2

RE[5]: That's cool.
by M.Onty on Wed 27th Feb 2013 16:18 in reply to "RE[4]: That's cool."
M.Onty Member since:
2009-10-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.


IE's compatibility mode is for viewing sites designed around IE5, IE5.5 & IE6 quirks. Therefore IE is only better at running broken code that was written specifically for it.

Reply Parent Score: 3