News

Microsoft: IE 8-Friendly Sites on the Rise

Microsoft cited progress on Internet Explorer 8 use on Tuesday, suggesting that more Web developers are trusting the user experience with its newest browser.

One of the ways Web developers can ensure users see Web content correctly is to compel IE 8 to use a more compatible mode. By adding code to their sites, Web developers can emulate IE 5 or IE 7 displays in a visitor's browser via a "compatibility-view list" in IE 8. Microsoft found that fewer Web sites are on that list, indicating greater trust in how the content displays in IE 8 standards modes.

Microsoft measured  the use of the compatibility-view list in high-traffic Web sites and found a decline in its use -- from 3,100 Web sites in March 2009 to "just over 2,000" Web sites now, according to a post by Marc Silbey, a Microsoft program manager, in Microsoft's IE blog.

The blog provides a diagram illustrating how IE 8 determines the document mode, which affects how the content gets displayed for the end user. Microsoft designed IE 8 to render "in the most standards-compliant way by default," according to the blog.

Microsoft's survey of high-traffic Web sites found that 41 percent used "almost standards mode," indicating that a Transitional HTML doctype was used on the Web site. "Quirks mode" was the next most popular doctype at 26 percent. Pure "IE 8 standards mode" was the choice of 19 percent of the Web sites, while "IE 7 standards mode" was used by 14 percent.

Developers can control how content renders by using the X-UA-Compatible meta tag to override IE 8 user settings. It's a stop-gap measure until developers -- who typically designed their sites to be compatible with the infamous IE 6 browser -- are ready for IE 8 standards mode. IE 6 has a reputation of being an unsecure browser that skirted the W3C's HTML recommendations in many cases, although it's still widely used.

The next set of controls resides in the user's compatibility-view settings in IE 8. If nothing is specified there, IE 8 checks the doctype to determine how the Web page will render, selecting either "IE 8 Standards, IE 8 Almost Standards or Quirks Mode," according to Microsoft's blog.

Microsoft provided its document mode options to give developers more time to prepare their Web sites for IE 8, according to Silbey.

"IE needs to support all of these Web platform variations to ensure that our broad, worldwide user base has the best experience," Silbey said in the blog.

Still, there was much grumbling in the comments section of the blog. Readers accused Microsoft of waiting a year to explain IE 8's document mode and having too many modes in the first place. Others wanted Microsoft to ditch its Trident layout engine for the WebKit rendering engine used by other browsers, such as Apple Safari and Google Chrome.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube