Why Google Chrome Frame Makes Mozilla Firefox Folks Uneasy
Table of Contents: — Mozilla's Mitchell Baker and Mike Shaver both lamented Google's release of Chrome Frame in blog posts. The browser experts, who helped Mozilla's Firefox browser reach 23.8 percent market share largely …
Context & Ripple Effects
Mozilla had flagged Google’s planned Chrome Frame plug-in two days before the release, setting up an unusual dispute between browser makers rather than a routine product launch. Microsoft had already argued that Chrome Frame introduced a security risk for Internet Explorer, giving Mozilla’s criticism a broader browser-governance frame.
First-order effects
- Mitchell Baker and Mike Shaver’s public criticism makes Chrome Frame an immediate point of friction between Google and Mozilla, whose Firefox team had helped build substantial browser share.
- Google must defend Chrome Frame not only as a product release but against objections from both Mozilla leaders and Microsoft’s security critique.
Second-order effects
- Microsoft gains support for keeping security, rather than browser features alone, at the center of its response to Google’s plug-in.
- Firefox faces pressure to explain why users should rely on its browser experience as Google promotes an alternative browser technology through Chrome Frame.
Third-order effects
- If browser makers increasingly deploy rendering technologies through plug-ins, competition shifts from winning a browser installation to controlling the web technologies users encounter inside another vendor’s browser.
- The dispute points toward browser security and interoperability becoming competitive weapons, with vendors contesting who bears responsibility when third-party browser components are introduced.
The trend: Browser competition is expanding beyond standalone applications into control over the components and standards delivered within rival browsing environments.