| Google Chrome Frame | |
|---|---|
 Internet Explorer 6 using Google Chrome Frame to render Wikipedia’s main page | |
| Developer | Google Inc. |
| Initial release | September 22, 2009 (2009-09-22) |
| Final release | 32.0.1700.107 (February 1, 2014; 11 years ago (2014-02-01)) [±] |
| Preview release | 32.0.1700.76 (January 13, 2014; 11 years ago (2014-01-13)) [±] |
| Written in | C++ |
| Engine | WebKit (based onKHTML) |
| Operating system | Microsoft Windows |
| Type | Replacementlayout engine |
| Website | www |
Google Chrome Frame was aplug-in designed forInternet Explorer based on the open-sourceChromium project, first announced on September 22, 2009.[1] It went stable in September 2010, on the first birthday of the project.[2] It was discontinued on February 25, 2014 and is no longer supported.[3]
The plug-in worked withInternet Explorer 6,7,8 and9.[3] It allowed suitably coded web pages to be displayed in Internet Explorer byGoogle Chrome's versions of theWebKitlayout engine andV8 JavaScript engine. In a test byComputerworld,JavaScript code ran 10 times faster with the plug-in on Internet Explorer 8.[4]
Development of Google Chrome Frame was required in order forGoogle Wave (nowApache Wave), which requiresHTML5, to function in Internet Explorer.
The first stable version supporting Non-Admin Chrome Frame was rolled out on August 30, 2011. The newer Chrome Frame installer ran at Admin level by default and fell back to Non-Admin mode if the user didn't have the necessary permissions on their machine.[5]
Web developers can allow their websites to use the plug-in by using the following code on their web pages:
<metahttp-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 theapplication/xhtml+xml MIME type even on Internet Explorer which normally does not support this MIME type for XHTML documents.[6] For a blanket rollout on an entire web site, an Apache server withmod_headers andmod_setenvif enabled can specify a header directive like this:
<IfModulemod_setenvif.c><IfModulemod_headers.c>BrowserMatchchromeframegcfHeaderappendX-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 fromMozilla[7][8] andMicrosoft[9] as Chrome Frame "can disable IE features and muddle users' understanding of Web security matters". With Google Chrome Frame installed, users can add thegcf: prefix to URLs to render them with WebKit and V8 instead of Internet Explorer's built-inTrident engine after enabling this feature via a registry setting. An update also brought the possibility to navigate pages in IE utilising WebKit/V8 without thegcf: prefix:[10]
| Registry key | Value | Function |
|---|---|---|
HKCU\Software\Google\ChromeFrame | AllowUnsafeURLs=1 (DWORD) | By adding thegcf: prefix to the URL in address bar, the page will load rendered with WebKit/V8 |
IsDefaultRenderer=1 (DWORD) | Makes WebKit/V8 the default rendering technique |
Google Chrome Frame communicated with Google's servers: it reported installation to Google, downloaded updates to Chrome Frame andGoogle's Safe Browsing list, and at the user's discretion could send Google usage statistics andcrash reports.[11]
