Rupam wrote:
> Why does not IE 8 pass the acid3 test?
(After waiting 10 minutes for my post to show up but did not, issued a
repost of this message. Ignore a duplicate if it appears.)
Because it employs HTML5 which has not yet been ratified. See
http://dev.w3.org/html5/spec/Overview.html. Notice it says "Draft"?
Firefox does better but is still not 100% (instead is 71%). Chrome got
100% but dropped a point for some link test. Safari is currently
getting 100%.
Some of the Acid3 tests use SVG (Scalar Vector Graphics) which IE does
not support. Microsoft came up with their own VML (Vector Markup
Language) but other web browsers use SVG (begrudgingly support VML);
http://www.w3.org/Graphics/SVG/WG/wi..._Origin_of_SVG and
http://en.wikipedia.org/wiki/Vector_Markup_Language. A real (aka good)
site will test which web browser is connected to it. If IE then they
present a web page or dynamically update it to use VML instead of SVG.
If not IE then they present a web page or dynamically update it to use
SVG. VML was submitted back in 1998 (
http://www.w3.org/TR/NOTE-VML);
however, W3 leaned to SVG group. Microsoft was obviously not going to
wait until ratification to implement VML in their web browser, just like
AcidTests.org and non-Microsoft web browsers are not awaiting for
ratification of HTML5 to use Web2 specifications from it.
That AcidTests will only use SVG shows their overt bias against IE. It
is as unfair a test as would be one that only employs Microsoft's
Silverlight and not include Flash or other contending script-controlled
content. VML is a standardized scalar graphics format as part of the
Open Office XML format that became part of ECMA Intl's standard in 2006
(ISO/IEC 29500:2008 and ECMA-376):
http://www.ecma-international.org/pu...s/Ecma-376.htm
Although a legitimate ECMA standardized document format, AcidTests
choose to ignore it. Gee, I wonder why? Ian Hickson who operates that
site is a member of WHATWG, "An unofficial [loose] collaboration of web
browser manufacturers and interested parties who wish to develop new
technologies designed to allow authors to write and deploy Applications
over the World Wide Web." Their charter (
http://www.whatwg.org/charter)
clearly shows they are pushing for HTML5 compliance (which is still a
draft). "The W3C HTML working group and the WHATWG are working on the
same specification, with the same editor" (
http://www.whatwg.org/).
From
http://en.wikipedia.org/wiki/WHATWG, you'll notice Microsoft isn't
included (they declined) in that "loose" group. AcidTests has their own
agenda to push based on who are their members.
Some web browsers are yanking some of the new features of HTML5 and
starting to support them (although the HTML5 could change anytime before
whenever it finally gets ratified, like maybe in 2012?). It would be
preferable if web browsers first focused on being fully HTML4.01
compliant before sucking in new stuff from HTML5.
Web browsers are bringing HTML5 features because they're all eager to
support Web2 and AJAX features (i.e., they're pushing the envelope
because web authors are). Personally I'd like to see Microsoft first
focus on severely improving the speed of their Jscript engine so it is
comparable in speed to Chrome and Safari.