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 354939
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: I agree with Microsoft on this
by lemur2 on Wed 25th Mar 2009 09:35 UTC in reply to "I agree with Microsoft on this"
lemur2
Member since:
2007-02-17

"The concern Microsoft has is that if we burnt [draft standards] into Internet Explorer 8 and passed Acid3 with 120 percent and then deploy it on so many machines, especially in the enterprise, [we have made draft standards de-facto standards] when the W3C will then want to innovate on the [evolving] standards..."

I totally agree with this.

"It surely is an interesting view on things, but it's also a flawed one. The standards tested by Acid3 might not be official standards just yet, but with Opera, WebKit, and Gecko all working towards supporting it, Trident could've just followed and make it the standard. This would've certainly earned Microsoft some good karma, something it could use in the browser market (what, with IE bleeding market share like a decapitated bunny)."

This is stupid. Why the heck do you want to make a draft standard the final standard without proper review? There is a REASON they are still in draft. What if a major issue was discovered. Oh, yeah, real good karma with that, right?

This kind of behaviour (just making something the defacto standard because you want/can) is the kind of thing Microsoft used to participate in with older versions of IE.

What if Microsoft implements some of the draft standard in a certain, but not technically incorrect, way and hen the final standard changes slightly? Whoops. You now have a proper (W3C) standard and one that is used by 90% of all browsers (IE). Great we are now back to square one and have solved nothing.

And no, they cannot just realise a x.1 version of IE to slightly change how they implement the standard to make it 100% compatable with the final version. That could break many many peoples websites.

Thom. This is probably the dumbest thing I've read from you. You don't even justify how it would ".earned Microsoft some good karma"


No, no, no. Just no. Don't fall for BS stories that Microsoft is feeding you.

Your scenarios just do not apply here.

A metaphor might help here: it is like a multi-story building ... you can start to build the second floor (after all, those plans have been finalised for over five years now) ... even if they haven't yet finally decided on the colour of the carpet in the penthouse.

There is no way that the final colour decided for the carpet in the penthouse will "break" the work you are doing now on the second floor.

All the other "builders" in the development area have finished building their second floor, and are well started on the third floor.

End metaphor. Get it now? No-one is changing the second floor, it has been approved for construction (as it is) for five years already. Build it, for goodness sake!

Edited 2009-03-25 09:40 UTC

Reply Parent Score: 6

Aragorn992 Member since:
2007-05-27

Hmmmm alright. In that case, fair point.

Reply Parent Score: 1