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.
Thread beginning with comment 355180
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Some Facts
by lemur2 on Thu 26th Mar 2009 11:43 UTC in reply to "RE: Some Facts"
Member since:

To be fair, the big missing elephant in the room is SVG. I don't think it's accurate to state that SVG has been out there (in usable browser form) for 8-9 years like some have been claiming, but more like 2-3 years in incomplete form (at least according to the history in Wikipedia).

Probably the IE folks decided that SVG was not high priority for this release. They may also still be unhappy about the rejection of VML.

The history of SVG on Wikipedia says this:

SVG 1.0 became a W3C Recommendation on September 4, 2001.
SVG 1.1 became a W3C Recommendation on January 14, 2003.
SVG Tiny 1.2 became a W3C Recommendation on December 22, 2008.
SVG Full 1.2 is a W3C Working Draft.

So the level asked for in Acid3, which is SVG 1.1, has only recently become available in those browsers that mostly pass Acid3 (that is, almost anything except IE).

That level of SVG has been a recommendation (i.e. stable) for over six years now. SVG 1.1 is the stable level, and that is all that is reasonably required to be considered standards compliant.

The additional SVG functions defined in level 1.2 Tiny are too recently recommended to expect to be implemented anywhere as yet, and the further functions defined in level 1.2 Full are still draft.

BTW, DOM level 2 compliance being missing in IE is almost as big an elephant in the room. As is the lack of a compliant JIT javascript compiler. Actually, we seem to have a bit of a huge roomful of elephants.

Edited 2009-03-26 11:47 UTC

Reply Parent Score: 3