Amit Joshi, Alex Russell and Mike Smith: To start using Google Chrome Frame, all developers need to do is to add a single tag:
<meta equiv="X-UA-Compatible" content="chrome=1">
That’s just so wrong on so many levels. What’s on the web site doesn’t even match the video. Instant legacy!
meta
and http-equiv
. They’re just overloading IE’s misguided quirksmode switch. As this is an IE plugin, I guess this decision won’t do much harm, because X-UA-Compatible is in IE anyway. An IE without the plugin will probably ignore this meta directive and use DOCTYPE to decide between quirks and standards mode, so maybe it’s even a good thing because it breaks the intended use of X-UA-Compatible.Mozilla planned to do something similar with ScreamingMonkey, but by hooking <script type="application/ecmascript;version=4">
and <script type="application/javascript;version=2">
, but that seems to have died with ActionMonkey.
Sigh, and your site has forgotten me again. Maybe a year isn’t long enough for a cookie, given the odds I’ll comment in the same browser in that time.