To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

How to transfigure the Wikipedia

Would you like Wikipedia to always look as professional and up-to-date? We have created a browser extension. It will enhance any encyclopedic page you visit with the magic of the WIKI 2 technology.

Try it — you can delete it anytime.

Install in 5 seconds
4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
Great Wikipedia has got greater.
.
Leo
Newton
Brights
Milds

Google Chrome Frame

From Wikipedia, the free encyclopedia

Google Chrome Frame
Developer(s)Google Inc.
Initial releaseSeptember 22, 2009 (2009-09-22)
Final release32.0.1700.107 (February 1, 2014; 10 years ago (2014-02-01)) [±]
Preview release32.0.1700.76 (January 13, 2014; 10 years ago (2014-01-13)) [±]
Written inC++
EngineWebKit (based on KHTML)
Operating systemMicrosoft Windows
TypeReplacement layout engine
Websitewww.chromium.org/developers/how-tos/chrome-frame-getting-started

Google Chrome Frame was a plug-in designed for Internet Explorer based on the open-source Chromium 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 with Internet Explorer 6, 7, 8 and 9.[3] It allowed suitably coded web pages to be displayed in Internet Explorer by Google Chrome's versions of the WebKit layout engine and V8 JavaScript engine. In a test by Computerworld, JavaScript code ran 10 times faster with the plug-in on Internet Explorer 8.[4]

Development of Google Chrome Frame was required in order for Google Wave (now 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 user didn't have the necessary permissions on their machine.[5]

YouTube Encyclopedic

  • 1/5
    Views:
    655 708
    54 868
    9 402
    35 258
    791
  • Introducing Google Chrome Frame
  • Using Google Chrome Frame
  • Google I/O 2010 - Using Google Chrome Frame
  • Google I/O 2011: HTML5 Today with Google Chrome Frame
  • Google Chrome Frame

Transcription

Hi! I'm Alex and I'm a Software Engineer at Google. I'm here to tell you about Google Chrome Frame, a new plugin, that brings open web technologies and Google Chrome's speedy rendering engine to Internet Explorer. We built Google Chrome Frame to help developers create rich, cutting edge web apps. To get there, web developers need access to technologies like HTML5's canvas tag and recent improvements in JavaScript performance. Some of these capabilities are not supported by Internet Explorer, especially its older versions. Developers still need to reach IE users, so they often invest lots of time and effort finding work-arounds, or sometimes they limit the functionality of their apps. With Google Chrome Frame, developers can design and build the apps that users want. They can target Google Chrome's advanced HTML engine, it's speedy V8 JavaScript runtime and all the other open web technologies in Google Chrome. This allows them to build apps that are faster and more powerful. To take advantage of Google Chrome Frame, all you need to do is add a single tag to the top of a page. When Google Chrome Frame detects this tag, it switches to Google Chrome's high-performance HTML engine. Other browsers that don't understand the tag, just render the page as normal. Since developers are fully in control of whether or not to start Google Chrome Frame, existing sites won't break. All of us on the team are excited about how much better the web can get. We've worked hard to make Google Chrome Frame simple, fast, and seamless, while staying true to the spirit of the open web. Google Chrome Frame is an open source project, so try it out on your sites, check out the code, and let us know how it goes so we can improve the web, together.

Deployment

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.[6] 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[7][8] and Microsoft[9] 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 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 user's discretion could send Google usage statistics and crash reports.[11]

References

  1. ^ "Introducing Google Chrome Frame". Chromium Blog. Retrieved 2020-08-14.
  2. ^ "Google Chrome Frame: Stable and Speedy". Chromium Blog. Retrieved 2020-08-14.
  3. ^ a b "Chrome Frame - The Chromium Projects". www.chromium.org. Retrieved 2020-08-14.
  4. ^ Amy Willis (2009-09-25). "IE8 browser runs faster with Google Chrome plug-in". The Daily Telegraph.
  5. ^ "Non-Admin Chrome Frame Reaches Stable Channel". Chromium Blog. Retrieved 2020-08-14.
  6. ^ "Google Chrome Frame Developer Updates". Chromium Blog. Retrieved 2020-08-14.
  7. ^ Shankland, Stephen. "Mozilla VP: Chrome Frame is the wrong answer". CNET. Retrieved 2020-08-14.
  8. ^ Keizer, Gregg (2009-09-29). "Mozilla slams Google's Chrome Frame as 'browser soup'". Computerworld. Retrieved 2020-08-14.
  9. ^ Fried, Ina. "Microsoft bashes Google's Chrome-in-IE plan". CNET. Retrieved 2020-08-14.
  10. ^ "Chrome Frame: Developer Guide - The Chromium Projects". Archived from the original on 2010-12-04. Retrieved 2020-08-14.
  11. ^ "Google Chrome Frame Privacy Notice". Archived from the original on 2011-08-25.
This page was last edited on 14 August 2023, at 21:44
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.
Contact WIKI 2
Introduction
Terms of Service
Privacy Policy