Linked by Thom Holwerda on Tue 24th Mar 2009 23:26 UTC, submitted by inkslinger
Internet Explorer Recently, Microsoft released Internet Explorer 8, which boasted much better standards compliance than previous iterations of the browser. While it passed the Acid2 test, IE8 failed miserably in the Acid3 test, and many people criticised Microsoft for it. Microsoft Australia's Nick Hodge has stated that Microsoft purposefully decided not to support Acid3, because the test tests against draft standards.
Permalink for comment 354936
To read all comments associated with this story, please click here.
Poor excuse!
by vasko_dinkov on Wed 25th Mar 2009 09:05 UTC
vasko_dinkov
Member since:
2005-09-13

That sounds reasonable at first glance but actually it is just a poor excuse for simply not being able to support ACID3 within the IE8 dev cycle.

It this is the real reason, why did they bother implementing stuff in IE8 like document.querySelector from the W3C Selectors API when it's still a draft spec too?

Reply Score: 2