Just what has Microsoft been doing for IE 7? 354
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?"
The Percentages (Score:5, Informative)
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
200...5 article? (Score:5, Informative)
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.
Re:The Percentages (Score:5, Informative)
Article from 2005 (Score:1, Informative)
Re:The Percentages (Score:4, Informative)
This article is a year old (Score:5, Informative)
Re:ACID2 - Whoopdeedoo! (Score:4, Informative)
jf
Re:Auto-boycot (Score:5, Informative)
Re:I vote de-facto standard (Score:2, Informative)
Then, they should get busy!
The government hasn't dealt with any issues in years.
Do we all know what year it is? (Score:3, Informative)
Let's be fair here and not criticize IE7 based on a year-old article that's talking about beta 1. If you've got gripes with beta 3's problems (which it does indeed have), then by all means, gripe away.
Re:IE developers use Firefox themselves (Score:5, Informative)
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! [edwards.name]). 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.)
Re:I vote de-facto standard (Score:3, Informative)
When buying a system from Dell, etc. Dell provides the support, NOT Microsoft.
That is the whole reason why an OEM copy of Windows costs less than the full retail version, it comes without support from Microsoft. It is intended to be supported by the OEM that puts it on the machine.
Last year, not last week (Score:4, Informative)
Re:Auto-boycot (Score:3, Informative)
Uh, they do. Except they're EVEN MORE unobtrusive about it.
I was curious, so I decided to check it all out in IE myself. The page opened fine, just with a SMALL header at the top:
"Please consider upgrading your Web browser
Internet Explorer doesn't properly support CSS standards (IE 52% vs. Firefox 93%). If you visit our site with Firefox or Safari, it works perfectly. NewsCloud recommends you upgrade to Mozilla's open source Firefox browser for a better experience with our Web site."
What's wrong with that?