KuraFire

More technical details about Google Chrome Frame

I also got curious about the User Agent strings that Chrome Frame embedded inside of IE might return. If you’ve spent any time with User Agent strings, you might expect a certain amount of schizophrenia, depending on where you look for them, either on the server side or the client side. I wrote a quick PHP script to echo out the User Agent as PHP sees it and to echo out the User Agent as javascript sees it. The server-side detection sees the browser as IE, with one tiny exception: it adds a string “chromeframe” to the User Agent that you could easily look for and act on. The client-side detection sees the browser as Google Chrome — the exact same User Agent as when you visit the page using the Chrome browser.

Please don’t ever do this. UA sniffing is unreliable, dangerous, and a main reason we’re having this problem with IE in the first place. The sooner we eradicate the practice of UA sniffing, the better the Web will be.

Instead, do feature detection. While that link focuses on HTML5 only, Modernizr does feature detection for CSS3 as well.

Source: jimray