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 354887
To read all comments associated with this story, please click here.
RE: Once in a blue moon...
by dvhh on Wed 25th Mar 2009 01:12 UTC in reply to "Once in a blue moon..."
dvhh
Member since:
2006-03-20

personally I always though that ACID browser test were a dick contest anyway. But their first focus were on interoperability ( it sure does trails away from this one ) between browser, now it seem that browser vendor target their rendering engine/DOM for this test.

So what are today's standard anyway? the (first) browser war didn't helped that much because of lazy web designer / browser dev, what about this (second) browser war it seems that webkit is gaining more and more traction because of the support of not yet standard features ?

current de-facto standard :
- full HTML support ( up to 4.1 ) / features of the html 5
- full XHTML support
- plugin support ( ie : adobe slow ass flash )
- full CSS 2.1
- CSS 3 support ( webkit devs will certainly define them while other would provide "compatible" implementation ) ( benchmark should be http://www.css3.info/preview/ ) ( example of fragmentation over not yet standard http://www.css3.info/preview/background-size/)
- SVG support
- fast jit javascript engine ( why not aot ?)
- XmlHttp async call support
- Canvas support ( needed to replace flash in 40% of the cases)
- PNG transparencies

And that might be all.

Anyway now Microsoft seem to be in the old Netscape place in this war. It is not about being standard, it's more about being future proof and regarding the deployment rate of IE7, how long would the user have to wait for a CSS 3 compliant IE 8.1/9 after the "validation" from the W3C ?

Reply Parent Score: 5