Linked by Thom Holwerda on Fri 22nd Oct 2010 22:11 UTC, submitted by google_ninja
Internet Explorer "There, I said it. Microsoft has been bombarding the media with claims about how much better IE9 is than all the other browsers, more HTML5 and CSS3 compliant than any other browser that ever existing and ever will. It's the only browser that passes all the tests they made up. And, Microsoft has finally implemented the CSS3 selectors that were implemented by other browsers back in, what? 2003? Because Microsoft has updated IE to support CSS3 selectors and rounded corners, they want us to believe that somehow IE9 magically supports the whole slew of CSS3 visual styling. I'm afraid it doesn't. As a matter of fact, IE9's support for CSS3 visual styling is so poor that the results are shocking."
Thread beginning with comment 446670
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Source code
by gmiretti on Fri 22nd Oct 2010 23:28 UTC in reply to "Source code"
Member since:

Apparently the source code is available in this post: and a demo at

You are right, he uses webkit specific properties like "-webkit-transform:" so the web app renders awful in Firefox.

Reply Parent Score: 15

RE[2]: Source code
by Hiev on Fri 22nd Oct 2010 23:47 in reply to "RE: Source code"
Hiev Member since:

Then that guy is an ignorant moron.

Reply Parent Score: 6

RE[2]: Source code
by sukru on Sat 23rd Oct 2010 00:32 in reply to "RE: Source code"
sukru Member since:

Thanks, I should've missed that.

But having half the CSS coded in webkit specific attributes, and then expecting other browsers to support them is not something normal.

Reply Parent Score: 4

RE[3]: Source code
by Kochise on Sat 23rd Oct 2010 17:55 in reply to "RE[2]: Source code"
Kochise Member since:

Remember Navigator's proprietary < blink> tag ?


Reply Parent Score: 2

RE[2]: Source code
by Gone fishing on Sat 23rd Oct 2010 06:36 in reply to "RE: Source code"
Gone fishing Member since:

Informative post +1

But why has css3 got browser specific properties? I thought we were trying to move away from that nonsense. Are other browsers supposed to implement these webkit properties?

Reply Parent Score: 2

RE[3]: Source code
by ssokolow on Sat 23rd Oct 2010 07:21 in reply to "RE[2]: Source code"
ssokolow Member since:

It's standard practice to use browser-specific properties until the standard is finalized so the browsers can retain backward compatibility if the syntax in the spec changes.

Reply Parent Score: 1