Recently, we tried to test our site in IE8 and found all the styles in the page are not applied properly.We know that we can’t always get a cross-browser result, but that’s mostly because IE6 blows. However, if we write standards-based code, test it in a browser like Firefox that has pretty good standards support, and then make minor tweaks for the broken browsers, the development process is much easier.
After some research, we found that during the IE7 beta concerned sites that looked fine in IE6 but looked bad in IE7. The reason was that the sites had worked around IE6 issues with content that – when viewed with IE7’s improved Standards mode – looked bad.
Now, when a site hands IE8 content and asks for Standards mode, that content would expect IE7’s Standards mode and not appear or function correctly. This creates a “get ready” call to action for site owners to ensure their content will continue to display seamlessly in IE8.
EmulateIE7 tells IE8 to display standards DOCTYPEs in IE7 Standards mode, and Quirks DOCTYPEs in Quirks mode. We believe this will be the preferred IE7 compatibility mode for most cases.
- On a per-page basis, add a special HTML tag to each document, right after the <head> tag
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
Using the IE=EmulateIE7 compatibility tag is a simple way for users to continue their current experience when browsing your site until you can update with more standards-compliant content. Although adding this tag will prevent most display issues, you may also need to update your site to properly detect IE8.
To my surprise, all the Microsoft sites have this tag implemented !!!