Google Chrome Frame
Internet Explorer 6 using Google Chrome Frame to render Wikipedia’s main page
|Initial release||September 22, 2009|
|Stable release||30.0.1599.101 (October 15, 2013[±])|
|Preview release||31.0.1650.48 (November 6, 2013[±])|
|Operating system||Microsoft Windows|
|Engine||WebKit (based on KHTML)|
|Type||Replacement layout engine|
Google Chrome Frame is a plug-in designed for Internet Explorer based on the open-source Chromium project. It went stable in September 2010, on the first birthday of the project. In June 2013 Google announced they would retire Chrome Frame, and will cease support and updates for the product in January 2014.
The first stable version supporting Non-Admin Chrome Frame was rolled out on August 30, 2011. The new Chrome Frame installer will now run at Admin level by default and will fall back to Non-Admin mode if the user does not have the necessary permissions on their machine.
Web developers can allow their websites to use the plug-in by using the following code on their web pages:
<meta http-equiv="X-UA-Compatible" content="chrome=1" />
This will cause the page to render in Chrome Frame for users who have it installed, without changing it for users who have not.
In February 2010, Google Chrome Frame was updated to also support deployment by HTTP headers, with a number of advantages, such as simplified sitewide support and support of the application/xhtml+xml MIME type even on Internet Explorer which normally does not support this MIME type for XHTML documents. For a blanket rollout on an entire web site, an Apache server with mod_headers and mod_setenvif enabled can specify a header directive like this:
<IfModule mod_setenvif.c> <IfModule mod_headers.c> BrowserMatch chromeframe gcf Header append X-UA-Compatible "chrome=1" env=gcf </IfModule> </IfModule>
Internet Explorer add-ons do not function on pages rendered using WebKit. There has been criticism concerning Chrome Frame from Mozilla and Microsoft as Chrome Frame “can disable IE features and muddle users’ understanding of Web security matters”. With Google Chrome Frame installed, users can add the
gcf: prefix to URLs to render them with WebKit and V8 instead of Internet Explorer’s built-in Trident engine after enabling this feature via a registry setting. An update also brought the possibility to navigate pages in IE utilising WebKit/V8 without the
|HKCU\Software\Google\ChromeFrame||AllowUnsafeURLs=1 (DWORD)||By adding the
|IsDefaultRenderer=1 (DWORD)||Makes WebKit/V8 the default rendering technique|
Google Chrome Frame communicates with Google’s servers; it reports installation to Google, downloads updates to Chrome Frame and Google’s Safe Browsing list, and at the user’s option can send Google usage statistics and crash reports.
- Chromium Blog: Google Chrome Frame: Stable and Speedy
- "Retiring Chrome Frame". Retrieved 13 June 2013.
- Amy Willis (2009-09-25). "IE8 browser runs faster with Google Chrome plug-in". The Daily Telegraph.
- Chromium Blog: Non-Admin Chrome Frame Reaches Stable Channel
- Russell, Alex (2010-02-09). "Google Chrome Frame Developer Updates". Google. Retrieved 2010-02-15.
- Shankland, Stephen (2009-09-29). "Mozilla VP: Chrome Frame is the wrong answer". CNet. Retrieved 2010-02-02.
- "Microsoft bashes Google's Chrome-in-IE plan".
- "Chrome Frame: Developer Guide - The Chromium Projects". Retrieved 2010-09-16.
- "Google Chrome Frame Privacy Notice".
- Google Chrome Frame home page
- Chrome Frame announcement
- Mozilla slams Google’s Chrome Frame as ‘browser soup’