I don’t claim to be an expert on web standards. In fact, very few people truly deserve the label of “expert” in this esoteric field. One is Jeffrey Zeldman, founder and majordomo of A List Apart, which I’ve been reading for years. Looking at my FeedDemon list, in fact, he’s the only web designer I consistently follow.
That means I haven’t been keeping up on the debate over how the community feels pover Microsoft’s decision to more fully support Web standards in IE8. Now, one thing they’re not going to do, apparently, is code IE so it passes the so-called Acid tests from the Web Standards Project.
I thought about this today as I was reading one persistent and annoying ZDNet commenter who seems fixated on ranting about the poor performance of IE8 Beta 2 on the Acid 3 test. I know that Microsoft could, if it chose to do so, build its browser to ace the Acid 3 test. Opera managed to do so. But Firefox has chosen not to. According to a chart Adrian Kingsley-Hughes published based on his testing, Their most recent builds come in at 71 out of 100 on the Acid 3 scorecard, and IE8 Beta 2 hits the low 20s.
I found this early 2008 article from Zeldman, in which he does a pretty good job of summarizing Microsoft’s “We can’t break the web” mentality, which has resulted in a feature called “version targeting.” I found this explanation especially compelling:
Non-standardistas have been writing JScript for years. While the CSS changes in IE7 may have “broken” a site’s layout, IE8’s JavaScript improvements could easily render a site useless. Real DOM support is a game changer. Enabled by default, it would bring many sites to their knees. That would break the web, and not in quotes. Providing IE8’s greater compliance on an opt-in basis is the only way to get everyone over the scripting hump.
Which brings us back to the question: Should a new browser pass some test, or should it move forward incrementally and continue to work as well as possible with the web as it exists today?
Frankly, I don’t care all that much about synthetic benchmarks. Getting a 100 on the Acid3 Test means that you will perfectly render a page that uses every known trick in the web standards guidebook, as written in that test. It does not mean that said browser will properly render the pages you visit every day or that your corporation uses on its intranet. Arguably, meeting that level of performance is more important. I would not want to have to explain to my CEO that no new sales came in this week because our new browser, which aced the Acid 3 test, barfs when it hits the order input page.
But I might be wrong. What I’d really like is some pointers to the experts out there who have already studied this subject and published well-considered opinions with lots of factual backup.
Anyone able to point me in the right direction? If you know your stuff, please help me out. I’ll assume that posting your comments here means you give me permission to use them (with attribution) in a follow-up post. And if it’ll help, I’ve got a couple of signed copies of Windows Vista Inside Out, Deluxe Edition for the most helpful, information-rich comments I get here.