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 354944
To read all comments associated with this story, please click here.
W3C standards
by 3rdalbum on Wed 25th Mar 2009 10:41 UTC
Member since:

I don't blame any browser manufacturer for deciding if and when to implement a new W3C 'standard'. The W3C creates virtually a new 'standard' every day for all sorts of completely inane things that maybe one or two people want to do with a web browser.

XForms? Timed Text? XML Events? OWL? Pronunciation Lexicon Specification? These are just a couple of examples of ill-considered, difficult-to-understand or completely useless W3C "standards" that have failed to take hold and as such as of absolutely no use to anybody. If Internet Explorer's developers tried to implement all these W3C 'standards', they wouldn't have time to add essential browsing features such as tabbed browsing and Javascript.

So, good on Microsoft for drawing the line somewhere. If Acid3 is finalised, then support it. Until then, assume it's another XAdES.

Reply Score: -1