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 355203
To read all comments associated with this story, please click here.
Laugh, Laugh, I thought I'd die
by deathshadow on Thu 26th Mar 2009 14:30 UTC
deathshadow
Member since:
2005-07-12

It seemed so funny to me...

Reading some of these comments are a hoot... Got news for folks - When did CSS2 exit draft? 1998... When did you start to see it's widespread use in the manner it was meant to because it was real world deployable? 2004-2005 ish.

Is support for CSS2 complete TODAY over a decade later? NOPE.

Just because the browsers support it does that make it deployable? Nope.


As I've said before several places I do not expect the majority of CSS3 to be real world deployable until sometime around 2015 to 2020.

... and I actually APPLAUD the IE team's deciding to try and focus on getting CSS2 correct before moving on to CSS3 - lands sake if only the mozilla folks bothered with that we'd not have a buggy inline-block that most developers are claiming works properly, and we'd have properly working colgroups, correct default positioning of elements inside inline-block ones, working @page, working attr=, fully styleable psuedo-elements, proper behavior of white-space on textarea, working pre-line, working display:run-in, properly triggering blur when onchange is tripped, properly implemented print properties... Hell, none of the browsers even implement float:right and float:left 100% correctly yet! (rarely an issue, involves line-collapse upwards)

As I said on the DECADE OLD UNRESOLVED bugzilla #915, maybe they should concentrate on finishing off HTML4 and CSS2 before having people wasting time on specifications that aren't even out of draft? (HTML 5 and CSS3)

Glad to see somebody listened, too bad it wasn't Mozilla.

Oh, and as to SVG, Adobe dropped it hard because they realized it couldn't compete with Macromedia Flash, so they took a page out of Symantec's playbook and bought out macromedia, buried their own product and rebranded Flash as their own...

Wait, no, my bad... Adobe has a history of doing that too - see what happened to Aldus.

Edited 2009-03-26 14:32 UTC

Reply Score: 2