Mozilla has sided with Microsoft in an attack on Google for its Chrome plug-in for IE
Mozilla executives have joined with Microsoft in the criticism of Google for its pitching of the Chrome Frame plug-in as a solution to Internet Explorer's poor performance. one executive arguing that Google's move will result in "browser soup."
Specifically, said Google, it was pushing Chrome Frame because it decided it wasn't worth trying to make its new collaboration and communications tool, Google Wave, work with IE. Google developers spent "countless hours" on tweaking Wave for IE, but gave up.
"We could continue in this fashion, but using Google Chrome Frame instead lets us invest all that engineering time in more features for all our users, without leaving Internet Explorer users behind," argued Lars Rasmussen and Adam Schuck of Google's Wave team last week.
Mitchell Baker, the former CEO of Mozilla and currently the chairman of the Mozilla Foundation, strongly disagreed with Google's tactic to slip Chrome inside IE.
"The overall effects of Chrome Frame are undesirable," Baker said in an entry to her personal blog. "I predict positive results will not be enduring and - and to the extent it is adopted - Chrome Frame will end in growing fragmentation and loss of control for most of us, including web developers."
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 websites. 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."
But Chrome Frame's biggest problem, said Baker, is that it cedes control to the site, not the person surfing. And that will just confuse users.
"For many people, Chrome Frame will make the web even more unknowable and confusing," Baker said. "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."
Microsoft took a different tack when it slammed Google for releasing Chrome Frame. The plug-in, claimed Microsoft, not only doubles the risk of attack - users have to worry about vulnerabilities in both IE and Chrome - but also breaks several features in its browser, including the private browsing mode.
Mozilla's vice president of engineering, Mike Shaver, weighed in alongside Baker, but also gave Google some advice.
"The user's understanding of the web's security model and the behaviour of their browser is seriously hindered by delegating the choice of software to the developers of individual sites they visit," Shaver said. "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 HTML 5.
"It would be better for the web if developers who want to use the Chrome Frame snippet simply told users that their site worked better in Chrome, and instructed them on how to install it," Shaver added.
He also panned Chrome Frame for some of the same reasons as Microsoft, but added several features "bricked" by the plug-in to the list, including IE8's Accelerators and accessibility tools.
Google's approach to solving the outdated browser problem is the path to madness, Baker concluded.
"Imagine having the Google browser-within-a-browser for some sites, the Facebook browser-within-a-browser for Facebook Connect sites, the Apple variant for iTunes, the mobile-carrier variant for your mobile sites," said Baker. "Each browser-within-a-browser variant will have its own feature set, its own quirks, and its own security problems. The result is a sort of browser-soup, where ... the web is less knowable, less understandable and certainly less manageable."
The Chrome Frame plug-in works with IE6, IE7 and IE8 on Windows XP and Windows Vista. It's available from Google's site as a free download .
Google did not immediately reply to a request for a reaction to Mozilla's criticisms of Chrome Frame.