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 355063
To read all comments associated with this story, please click here.
Member since:

I say this because I remember that Opera announced that it was the first browser to pass ACID3. Later that week, ACID3 itself was tweaked (to fix some problem or whatever). That tweak caused Opera to no longer pass ACID3. The Opera team made a new release to re-pass ACID3. This showed that Opera coded against ACID3, not against the "standards" that ACID3 is supposed to test. Opera passes ACID3, but does it really support the "standards" in question in a robust manner? Not if they have to update Opera whenever ACID3 changes.

Microsoft could have done like Opera did and code against ACID3, even if they didn't robustly support the standards in general. But it's a waste of time, means nothing except a checkbox on the "features" list.

Let the "standards" become real standards, then support them accordingly, I say.

Reply Score: 3