'IE8 Does Not Pass Acid3 Because Standards Not Official'
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.
E-mail Print r 7   · Read More · 81 Comment(s) http://osne.ws/gcp
Thread beginning with comment 354946
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: He should be...
by kaiwai on Wed 25th Mar 2009 11:15 UTC in reply to "RE: He should be..."
kaiwai
Member since:
2005-07-06

Sure. And then, face the flak that they will receive for sure when applications and pages that were made targeting those drafted standards break as a result of the changes. Because it's Microsoft we're talking about, and you know, no matter how they play it, they cannot win.


How many of these specifications are changed on whim with no considerations of browsers who have implemented them in the draft form? if you're going to make such bold claims about compatibility as the standard rapidly evolves; show me a case scenario in Firefox, Opera or Webkit where a draft standard has been adopted, the standard has changed, the browser is changed to be compatible with the new standard - and a website is broken.

Reply Parent Score: 2

RE[3]: He should be...
by lemur2 on Wed 25th Mar 2009 11:34 in reply to "RE[2]: He should be..."
lemur2 Member since:
2007-02-17

"Sure. And then, face the flak that they will receive for sure when applications and pages that were made targeting those drafted standards break as a result of the changes. Because it's Microsoft we're talking about, and you know, no matter how they play it, they cannot win.


How many of these specifications are changed on whim with no considerations of browsers who have implemented them in the draft form? if you're going to make such bold claims about compatibility as the standard rapidly evolves; show me a case scenario in Firefox, Opera or Webkit where a draft standard has been adopted, the standard has changed, the browser is changed to be compatible with the new standard - and a website is broken. "

Precisely so.

Or even better ... you could ask ... "please identify any change whatsoever in any of the the web standards DOM level 2, SVG 1.1, or SMIL 2.1 since these have been first published many years ago". (These are some of the few that are required for Acid3 compliance).

We could also ask "Please identify anything in the higher (and still draft) levels of these standards (such as DOM level 3, or SVG 1.2) that in any way affects anything already standardised at a lower level."

Once these nonexistent "changes" to existing levels have been "identified" then we can perhaps move on to the nonexistent websites "broken" by draft standards (that no browser implements yet anyway).

Edited 2009-03-25 11:36 UTC

Reply Parent Score: 3