Google just released Chrome Frame a plug-in for Internet Explorer that makes IE act like Google’s Chrome browser.
Something of a peanut-butter-in-my-chocolate value proposition.
Considering Internet Explorer’s historic support for @font-face and that Google hasn’t formally turned @font-face support on in Chrome, I wondered if fonts delivered by Kernest would render as expected.
Yes. Just as expected.
Internet Explorer still requests and renders the EOT fonts like it has for decades.
Chocolately peanut butter, yum.
Nope. I was wrong. Chrome Frame breaks Internet Exploreres @font-face support.
Oh the irony of a browser promising better web technology support removing @font-face support.
So, What caused the false positive?
Chrome Frame doesn’t automatically activate itself upon installation (not what I expected). ‘Enabled’ isn’t ‘activated’. Big thanks to Paul Irish for pointing this out.
How to test for yourself load this URL in Chrome Frame
cf:http://kernest.com
The ‘cf:’ forces rendering in Chrome’s Webkit engine.
Richard – on the question of IE-Tab in Firefox: Yes, the IE engine calls EOT files and renders the font. Though, I’m happy to be proven wrong.