Why Google Chrome Frame Makes Mozilla Firefox Folks Uneasy
The plug-in launched one week before Google's extended preview of Google Wave, which leverages HTML5. Microsoft protested the technology, arguing that it breaks IE 8's privacy features and poses a security threat.
"Image you download Chrome Frame. You go to a website. What rendering engine do you end up using? That depends on the website now, not on you. And if you end up at a website that makes use of the Chrome Frame, the treatment of your passwords, security settings, personalization, all the other things one sets in a browser is suddenly unknown. Will sites you tag or bookmark while browsing with one rendering engine show up in the other? Because the various parts of the browser are no longer connected, actions that have one result in the browser you think you're using won't have the same result in the Chrome browser-within-a-browser. "At first glance this looks like it might be a useful option, offering immediate convenience to website developers in alleviating a very real pain. But a deeper look reveals significant negative repercussions."Shaver echoed Microsoft when he noted running Chrome Frame within IE bogs down private browsing mode or Microsoft's other security controls. "The user's understanding of the Web's security model and the behavior of their browser is seriously hindered by delegating the choice of software to the developers of individual sites they visit," Shaver wrote. "It is a problem that we have seen repeatedly with other stack plug-ins like Flash, Silverlight and Java, and not one that I think we need to see replayed again under the banner of HTML5."