Just what has Microsoft been doing for IE 7?

Jeff Reifman writes "Last week, Windows columnist Paul Thurrott ripped into Microsoft for ignoring CSS standards with its upcoming Internet Explorer 7.0. "Microsoft has set back Web development by an immeasurable amount of time. My advice is simple: Boycott IE. It's a cancer on the Web that must be stopped. IE isn't secure and isn't standards-compliant, which makes it unworkable both for end users and Web content creators." With the redesign of my own site last month, I discovered just how non-compliant IE is with basic CSS: IE 52% vs. Firefox 93%. Is Microsoft purely incompetent and tone-deaf to customers — or simply counting on IE's non-compliance remaining a de-facto standard?"

Comments

The Percentages

[neonprimetime]

CSS 2.1 standard support:
IE 6: 52%
IE 7: 54%
Firefox 1.5: 93%
Opera 8.5: 93%
Opera 9: 96%

Ok, so I agree that the numbers seem to be good estimates, about right. But how on earth do they actually come up with these percentages? Is is a simple cumulative count of all css tags and attributes that work vs. don't work? Or do some have more weight than others? Seriously, they seem like fabricated numbers ... just like the /. article earlier today about how wide the universe is.

Re:The Percentages

[RonnyJ]

Here's the link that goes over all the figures: http://www.webdevout.net/browser_support_summary.p hp?uas=IE6-IE7-FX1_5-OP8-OP9

200...5 article?

[cpct0]

Unless they are mistaken, this is a 2K5 article. And it talks about the beta 1 release, I got beta 3.

Now on the topic of better CSS, I think IE7b3 is better than what is advertised in that article. It's still far from perfect though.

This article is a year old

[epohs]

Am I taking crazy pills, or is this article not over 1 year old? [ August 02, 2005 ]

Re:Auto-boycot

[envelope]

Apparently Newscloud tried that, and it just made a lot of people mad.

Re:IE developers use Firefox themselves

[loquacious d]

The "IE7" Javascript library by Web guru Dean Edwards has helped me a lot with the IE6 blues.

It allows IE6 to render transparent PNGs (using ActiveX[?] hooks built-in to IE that allow it to render 8-bit transparency, but is mysteriously not enabled for PNGs by default) and programmatically alters the DOM and parsed CSS to enable complex subselectors and a smattering of CSS2/3 selectors as well (including fixed background positioning!). It adds ~20K to pages using it, but it's a one-time cost as IE caches Javascript.

It's not a magic bullet, and sometimes causes issues itself, but definitely worth a look. Cause no one likes hacking their carefully-constructed divs back to tables, just to support a broken POS browser. (I also enjoy the irony that third-party Javscript hackers seem to be able to make more progress with IE's CSS compatibility than the actual IE team.)

Last year, not last week

[jazir1979]

This article is over a year old, the poster got it totally wrong. Does anybody have any info on whether the comments are still relevant in the latest IE7? I have no reason to expect that they aren't, but just checking.