Hmmm, this is interesting. Google's had spotty luck trying to push its Chrome browser to users, but now it's come out with Google Chrome Frame to embed Chrome's functionality inside Internet Explorer. What a sweet Peanut Butter Cup of an idea.The idea of embedding one browser's functionality inside another browser isn't new. Firefox users have IE Tab, for example, to run sites that absolutely require IE to run. With IE Tab the user can specify a list of sites and/or file extensions that should always be opened in an IE tab. That approach is problematic at times because the user isn't always the best person to determine whether the site works correctly with a particular browser. It may take trial and error on the user's part to determine that the site is breaking because it requires IE.

Google Chrome Frame lets web page developers specify that their page would really prefer to be rendered in Chrome rather than IE. Once the plugin is installed, the author of a web page can specify that IE should use the Chrome Frame plugin by putting a single tag into the top of the document:

If some other browser is in use, or if the user has IE with the plugin not installed, the page renders just like it normally would. If, however, the Chrome Frame plugin is installed in IE, the page is rendered using the Google Chrome engine even though it's still within the IE application.

This sort of browser-in-browser solution could be great for developers that want to support IE6 users without having to deal with IE6 quirks. They'd just add the tag to their site and tell IE6 users that they'd be supported only with Google Chrome Frame. (IE7 and IE8 aren't as problematic, so most developers can build a site that supports them with or without Chrome Frame.) The biggest problem I see is that many IE6 users are dealing with locked-down systems and won't have the authority or ability to add the plugin. If they could do that, they'd also be able to upgrade their browser!