On Thu, Feb 4, 2010 at 8:17 AM, Nimish Gautam ngautam@wikimedia.org wrote:
Hey all,
I really want to turn on Google chrome frame support for the mediawiki projects:
http://code.google.com/chrome/chromeframe/
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
The issues log at the bottom of the developers guide indicate this is not ready for prime time - i.e. printing doesn't work.
http://code.google.com/chrome/chromeframe/developers_guide.html
More fundamentally, the _user_ should control when a different renderer is used for websites; not the website! Currently this can be done with registry keys.
HKCU\Software\Google\ChromeFrame\OptInUrls
Hopefully they add a GUI to configure the OptIn list, and the ability to import a whitelist like Adblock and IETab.
fwiw, Mozilla-in-IE was at a similar stage three years ago.
http://starkravingfinkle.org/blog/2006/12/xule-what-if/
-- John Vandenberg