// 06.Nov.2009

Handling IE8: Use Chrome if Available, else Fallback to IE7

Joen Asmussen presents a method of directing IE8’s rendering engine:

The new rendering engine of IE8 was supposed to be more standards compliant, yet the CSS engine still follows Microsoft’s own rules, so the net result is that IE8 still can’t render advanced CSS layouts. The solution is to add a meta tag to tell IE8 to use the IE7 rendering engine; then you don’t have to target two browsers.

Then Google launched Chrome Frame which embeds Google Chrome’s superior rendering engine to IE. But it’s a plugin so it has to be installed and it has to be invoked using a meta tag.

Combining the two meta tags, so that we use Chrome Frame if available, but fall back to using IE7’s rendering engine if not, results in this meta tag:

<meta http-equiv="X-UA-Compatible" content="chrome=1; IE=7" />

Joen tested this on a recent site and tells us that it works as advertised.

Handle IE8: Use Chrome Frame If Available, Fallback To IE7 originally appeared on Noscope on November 2nd, 2009.

Last Revision: November 6th, 2009 at 07:53

2 Comments for “Handling IE8: Use Chrome if Available, else Fallback to IE7”

  1. It works so well, in fact, that it’s now part of my standard templates from which I develop anything.

  2. That’s really cool Joen. I’ve been using the Chrome Frame call ever since it was available and have even retro-fitted it to many of my client’s sites (with their approval of course).