Wow … Mozilla sides with Microsoft over Google’s Chrome Frame plugin

It was expected that Microsoft would attempt in some fashion to downplay Google’s Chrome Frame plugin that is designed to replace Internet Explorer’s web rendering engine with the one that power’s Google’s own Chrome browser. Of course they didn’t let us down in that fashion calling the plugin as a security threat for users of IE and the Internet. What wasn’t really expected was for Mozilla to come out publically on the same side of the fence as Microsoft.

Google’s reasoning for creating and releasing the plugin is that they just couldn’t get IE to play nice with their upcoming release of Google Wave so rather than wasting valuable time trying they created the Chrome Frame plugin.

While Mozilla agreed with Microsoft about the security issues Mitchell Baker, CEO of the Mozilla Foundation, argues that it could end up being detrimental to the user experience

According to Baker, Chrome Frame’s browser-in-a-browser will confuse users and render some of their familiar tools useless. “Once your browser has fragmented into multiple rendering engines, it’s very hard to manage information across Web sites. Some information will be manageable from the browser you use and some information from Chrome Frame. This defeats one of the most important ways in which a browser can help people manage their [Web] experience.”

Source: Computer World – Mozilla slams Google’s Chrome Frame as ‘browser soup’

In addition vice president of Mozilla Mike Shaver had this to say in a cnet interview

Specifically, Shaver said Chrome Frame can disable IE features and muddle users’ understanding of Web security matters. And users of the reviled IE 6 browser, he added, often won’t be able to run Chrome Frame anyway because their computer is locked down to prohibit changes or lacks sufficient power in the first place.

“As a side effect, 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. 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,” he said.