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 354952
To read all comments associated with this story, please click here.
MS is only partially right
by KugelKurt on Wed 25th Mar 2009 11:46 UTC in reply to "Fair enough"
KugelKurt
Member since:
2005-07-06

MS is right in this respect that draft standards should not be widely used, but that doesn't mean that a rendering engine shouldn't implement them.
This helps finding bugs early on and tweaking the rendering engine to support the final standard is easy when almost every foundation is laid. MS once again wants to hold back web innovation by beginning to implement standards years after they are final.

Microsoft has MSDN to tell web developers that a set of implemented features is work in progress. Web devs may use them internally for preparing the next release of their web site, but should also be aware that changes can occur and that those features should not be used until a final standard is agreed upon.

Reply Parent Score: 2