Google Chrome Frame – Wikipedia

Plug-in designed for Internet Explorer based on the open-source Chromium project
Google Chrome Frame was a circuit board designed for Internet Explorer based on the open-source Chromium project, inaugural announced on September 22, 2009. [ 1 ] It went stable in September 2010, on the first gear birthday of the project. [ 2 ] It was discontinued on February 25, 2014 and is no retentive supported. [ 3 ] The circuit board work with Internet Explorer 6, 7, 8 and 9. [ 3 ] It allowed appropriately coded network pages to be displayed in Internet Explorer by Google Chrome ‘s versions of the WebKit layout locomotive and V8 JavaScript locomotive. In a test by ComputerWorld, JavaScript code ran 10 times faster with the circuit board on Internet Explorer 8. [ 4 ] Development of Google Chrome Frame was required in arrange for Google Wave ( immediately Apache Wave ), which requires HTML5, 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 exploiter did n’t have the necessary permissions on their machine. [ 5 ]

deployment [edit ]

Web developers can allow their websites to use the circuit board by using the follow 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 besides support deployment by HTTP headers, with a count 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. [ 6 ] For a across-the-board rollout on an integral web site, an Apache waiter with mod_headers and mod_setenvif enabled can specify a header directive like this :

  

mod_setenvif.c

>

mod_headers.c

>

BrowserMatch chromeframe gcf Header append X-UA-Compatible "chrome=1" env=gcf

Internet Explorer add-ons do not function on pages rendered using WebKit. There has been criticism concerning Chrome Frame from Mozilla [ 7 ] [ 8 ] and Microsoft [ 9 ] as Chrome Frame “ can disable IE features and addle users ‘ agreement of Web security matters ”. With Google Chrome Frame installed, users can add the gcf: prefix to URLs to render them with WebKit and V8 alternatively of Internet Explorer ‘s built-in Trident locomotive after enabling this feature via a register setting. An update besides brought the possibility to navigate pages in IE utilising WebKit/V8 without the gcf: prefix : [ 10 ]

Registry key Value Function
HKCU\Software\Google\ChromeFrame AllowUnsafeURLs=1 (DWORD) By adding the gcf: 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 and Google ‘s Safe Browsing list, and at the drug user ‘s discretion could send Google use statistics and crash reports. [ 11 ]

References [edit ]

informant : https://coinselected.com
Category : crypto topics

Leave a Reply

Your email address will not be published.