Using Google Chrome Frame
Articles Blog

Using Google Chrome Frame

October 9, 2019


Hi! I’m Alex, I’m a Software Engineer
here at Google and I work on Google Chrome Frame — a plug-in that’s bringing HTML5
and rich, modern web apps to IE 6, 7, and 8. We launched a developer preview of the
plug-in last Fall. Since then we’ve been working hard to improve privacy, security,
and ease of deployment. We’ve also dramatically improved the performance of the plug-in.
A stable version of Google Chrome Frame is now available. Users of the beta will be automatically
updated to it and because Google Chrome Frame is out of beta, you can now build rich apps
with HTML5’s audio, video, and canvas tags without resorting to heavyweight shims and
frameworks that can slow down your site. New features like CSS animations and SVG work
great in Google Chrome Frame, and I’m certain that once you develop sites with modern web
technology, you’ll never want to go back. So how do you make your site work with Google
Chrome Frame? Once installed, Google Chrome Frame inspects
pages served to IE, looking for a special HTTP header or META tag.
Adding the meta tag to your site is simple, but remember that it should go at the very
top of your documents. If it’s too far down, the plug-in might not see the tag.
The fastest and most reliable way to trigger page rendering in Google Chrome Frame is by
using the HTTP header. Adding the header site-wide is often a simple
matter of including the right directives in a template or in your web server configuration.
Here we’ll add a header in an Apache configuration, restart the server, and see that when we visit
the site again we can right-click to use Chrome’s Web  Inspector… which is how we know the
page is being rendered with Google Chrome Frame.
Scripts like CFInstall and Modernizr can help you prompt users without the plug-in to upgrade
or install Google Chrome Frame. Prompting users is totally optional though, and users
who don’t have the plug-in just get IE’s existing behavior.  Check out the documentation
at code.google.com/chrome/chromeframe for details, but don’t worry, we’ve worked
to keep that part simple too. Thanks to HTML5, your rich apps can shine
without proprietary plug-ins and now, thanks to Google Chrome Frame, you don’t even have
to leave users of legacy browsers behind. Thanks for listening and for adding the headers
to your next HTML5-powered project.

Only registered users can comment.

  1. интересно он долго глаза пальцами тер, что бы выглядеть красноглазым гиком… ?

  2. Like said before, adding custom meta tags for specific browsers is exactly what we should NOT be doing.
    Also, providing this for IE6 is just plain stupid. IE6 should be dropped and replaced with either a newer version or a different browser entirely.
    Providing this for outdated (and now unsupported, beside highly critical flaw patching) browsers only gives the remaining people another reason not to upgrade/replace it.

    Just now major websites (ie, facebook) are dropping IE6 support.

  3. i'm a programmer but i don't have much interest on web development, recently i got occupied with django, but i never wanted to "dirt" my hands with css and templating in general. With google frame i started to think about it 😀

  4. my computer wont let me download google chrome frame and says i have an unexpected failure and I need help with it

  5. using ie9 and i have chrome. chrome frame plug-in on ie9 is crashing shockwave flash on youtube. looks like many people are having this issue using chrome?

  6. What's the point if the user has to install a plugin?
    The problem with IE isn't just that it's bad, but that its users use outdated software and DO NOT install/upgrade it.

    My grandmother would never be able to install Google Chrome Frame. 🙁
    Good effort though, keep it up guys 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *