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 354913
To read all comments associated with this story, please click here.
Stupid Question...
by JPowers on Wed 25th Mar 2009 05:22 UTC
JPowers
Member since:
2007-11-10

The WEBKIT team know that CSS 3.1 isn't final; so, they prefix "WEBKIT-" before all non-standard and non-final standard tags. This is the recommended method of adding non-standard features to your browser.

Why can't Microsoft support the current standards in full CSS 2.1, and SVG 1.1. They could then add the "IE-" prefix to the CSS3.1 elements and SVG 1.2 elements. It is always assumed that the behavior of "Browser_Tagged" elements are subject to change in the future and you should use at your own risk. When the standard becomes finial the developers can verify that they implemented the element correctly and then remove the prefix tags.

Reply Score: 3

RE: Stupid Question...
by lemur2 on Wed 25th Mar 2009 06:10 in reply to "Stupid Question..."
lemur2 Member since:
2007-02-17

Why can't Microsoft support the current standards in full CSS 2.1, and SVG 1.1.


Yes, that would be good enough, and would pass the relevant bits of Acid3.

They could then add the "IE-" prefix to the CSS3.1 elements and SVG 1.2 elements.


No need for IE to try to implement what is still in draft, just what levels have been finalised will do.

A list is here:

http://en.wikipedia.org/wiki/Acid3#Standards_tested

There is no need yet for any SVG level 1.2 elements or CSS level 3 elements.

Reply Parent Score: 4