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 355079
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Poor excuse!
by jayson.knight on Thu 26th Mar 2009 00:38 UTC in reply to "Poor excuse!"
jayson.knight
Member since:
2005-07-06

It this is the real reason, why did they bother implementing stuff in IE8 like document.querySelector from the W3C Selectors API when it's still a draft spec too?


Because compared to some of the other stuff, this is actually useful in the real world?

Reply Parent Score: 1

RE[2]: Poor excuse!
by lemur2 on Thu 26th Mar 2009 03:11 in reply to "RE: Poor excuse!"
lemur2 Member since:
2007-02-17

"It this is the real reason, why did they bother implementing stuff in IE8 like document.querySelector from the W3C Selectors API when it's still a draft spec too?
Because compared to some of the other stuff, this is actually useful in the real world? "

What you meant to say, surely, was that "unlike other stuff, the document.querySelector from the W3C Selectors API doesn't achieve, in an open standards way, functionality which we wish to be kept as lock-in for Silverlight".

As they say on slashdot ... there, fixed it for you.

Edited 2009-03-26 03:12 UTC

Reply Parent Score: 4

RE[3]: Poor excuse!
by jayson.knight on Thu 26th Mar 2009 03:18 in reply to "RE[2]: Poor excuse!"
jayson.knight Member since:
2005-07-06

No worries, I've seen your mis-information all over this thread and was waiting for your response.

Browsers are free, no one cares about lock-in...if you don't like what a browser does (as an end user), then move on. If you don't like what it does (as a developer) then don't develop for it, or figure out ways around whatever isn't working for you.

Sometimes I wonder if the only people who jump up and down screaming "standards standards standards" are people who've never actually developed real world web apps, simply because they have nothing better to do.

Have you ever wondered why these standards are still just in 'recommended' or 'draft' standard? Because no one out in the real world of web development cares about them...at least not the ones mentioned over and over in this thread.

Reply Parent Score: 1