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 553802
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: That's cool.
by avgalen on Wed 27th Feb 2013 11:44 UTC in reply to "That's cool."
avgalen
Member since:
2010-09-23

It renders the same in IE10 on Windows 8 as in Chrome on Windows 8 (meaning badly). However, when I press the compatibility view in IE10 it renders "perfectly"

Conclusion: Both are standard compliant, but IE10 is better at rendering bad code then Chrome

I can't make a comparison with older IE's, but why would I want to use an older IE anyway?

Reply Parent Score: 2

RE[2]: That's cool.
by Lennie on Wed 27th Feb 2013 12:24 in reply to "RE: That's cool."
Lennie Member since:
2007-09-22

This is not true.

Different browsers render different broken HTML in different ways.

You can find broken HTML which renders better in Chrome, Firefox or Opera than IE too.

Also have a look at my other comment:
http://www.osnews.com/permalink?553804

When you open the source code of the page it says Frontpage, not sure if that was actually used, if so my guess is that Frontpage created a page which is broken, but broken in a way that still displays correctly in IE.

Edited 2013-02-27 12:26 UTC

Reply Parent Score: 2

RE[3]: That's cool.
by smashIt on Wed 27th Feb 2013 12:48 in reply to "RE[2]: That's cool."
smashIt Member since:
2005-07-06

When you open the source code of the page it says Frontpage, not sure if that was actually used, if so my guess is that Frontpage created a page which is broken, but broken in a way that still displays correctly in IE.


the last frontpage-release was 2003
i'd say the site is as standards-complient as it was possible back then
which means there were no standards

Reply Parent Score: 2