Internet Explorer 8 and Web Standards
Wednesday, August 13th, 2008 Brandon Gregory
For all non-Web-designers out there, Web design has become more of a science and less of a trial-and-error exercise in patience in the recent years due to Web standards. Web standards, put out by the World Wide Web Consortium (W3C), dictated the way HTML and CSS were to be interpreted by browsers. So all of the sudden, it wasn’t up to browsers to figure this out—there was a standard that all browsers should adhere to. Well, that was the thought.
Internet Explorer has been around far longer than Internet standards have been popular. Microsoft was used to making up their own rules and figuring out how to best display websites. In their defense, they actually did a pretty good job—they had one of the best browsers around, pre-standards, and they’re still the most popular browser. But once standards caught on, those proprietary rules made Web design a nightmare. This was due to other popular browsers—namely Mozilla Firefox—being almost completely standards-compliant. Internet Explorer 6 was mostly standards-compliant, but still missed the mark considerably. Those little quirks in Internet Explorer 6 often made us re-code perfectly coded websites, and, in some cases, provide entirely separate code for Internet Explorer.
Internet Explorer 7 was a mixed blessing when it came out (for us, anyway). It was much more standards-compliant, and Microsoft actually saw the error of their IE6 ways and made Internet Explorer 7 a priority Windows update for all Windows users. So why a mixed blessing? Websites that had separate code for IE6 were suddenly “broken” in IE7. This was mostly due to websites not being built properly in the first place, but that didn’t stop the flood of hate-mail that Microsoft probably received on their new baby.
(I should also point out that IE7 had its own quirks that did cause standards-compliant Web designers some headaches. But the problems solved by IE7 greatly outweighed the problems caused.)
“Don’t break the Web.” That became Microsoft’s mantra during the initial development of IE8. In early 2008, they announced something called Version Targeting that would be implemented in IE8. Although IE8 was being developed for further adherence to standards, IE8 would interpret websites exactly like IE7 unless the website specifically asked to be interpreted by updated rules. This would also apply to IE9, IE10, and IE32—they would all interpret websites just the same as IE7 unless asked not to.
While this may have seemed like a good idea to the development team, which likely received a plethora of negative content about the latest incarnation of their browser, and to Web designers who built to browser standards rather than Web standards, it angered standards-compliant designers who wanted to see even more adherence to standards on the Web. Some of us came to see why Microsoft made the decision; others (like myself) remained angry about it, seeing it as a hindrance to progress toward a standards-compliant Web.
On March 3, Microsoft announced that they have reversed this decision. IE8 will now, by default, interpret pages in the most standard compliant way it can. The good news for designers worried about IE8 “breaking the Web” is that they can actually set their pages to request to be interpreted using IE7 standards. So version targeting is still around—only now, it’s the opt-in rather than the default. This is good news for the industry, and even better news for “standardistas” like myself.
So what does this mean for you, the non-Web-designer? Make sure your websites are being built to standards. Ask that your websites be built in XHTML 1.0 rather than HTML 4.01, and ask to make sure your code validates against the rules set forth by the W3C. As browsers move in that direction, compliance to Web standards is going to be more and more important, and early work will reduce the amount of adjustment needed whenever a new browser comes out. As an added bonus, it also gives you bragging rights in Web designer circles.

