Firefox, Chrome To Get 'Metro' Treatment for Windows 8
- By Kurt Mackie
- March 15, 2012
Browser makers face an unfamiliar hurdle with Windows 8, but both Mozilla and Google said they are building browsers that will work with the new operating system, with Opera Software also considering it.
Windows 8, which is now available for testing as a "consumer preview," essentially has two user interfaces based on the new Windows Runtime. The first is the "desktop" UI, which displays applications with the familiar chromed look, as seen with Windows 7-based apps. The second is the "Metro" UI, which runs in a full-screen chromeless mode and is optimized for touch.
Windows 8 supports those two browser experiences through Microsoft's Internet Explorer 10 browser. Essentially, IE 10 is available as two separate browsers supporting two different UIs in Windows 8.
Windows 8 users might expect to use other browsers than IE 10, and it seems that Microsoft will allow it, except that earlier IE versions (such as IE 9) won't be allowed to run on Windows 8, according to Microsoft's IE 10 FAQ. Other browser makers, such as Mozilla, Google and Opera, that are building for Windows 8 can do so, but they face certain requirements. For instance, they have to build something called a "Metro style enabled desktop browser," which is a Microsoft term encompassing certain specs for Windows 8-based browsers.
Metro-Style Enabled Desktop Browsers
Despite the "Metro style enabled desktop browser" terminology, a Microsoft whitepaper (Word .DOC) on the subject indicates browsers built to this spec will support both desktop and Metro UIs. The catch is that Metro-style enabled desktop browsers have to be the default browser to work on the Metro side.
A blog post by Mozilla Firefox developer Brian R. Bondy confirmed that the new Firefox browser being developed for Windows 8 can only run in the Metro mode if it is set as the default browser. He added that "this is a decision made by Microsoft." No technical reason was given.
Microsoft, for its part, claims in its whitepaper that this arrangement with the default browser setting requirement works the same as it did with Windows 7 -- that is, a default browser needs to be specified. However, the Metro UI is a new addition to the operating system in Windows 8, and staying true to that experience also seems to be a reason for the default browser restriction, according to Microsoft's whitepaper.
"A Metro style enabled desktop browser can be thought of as a desktop browser that can also participate in the new Metro style experience," the whitepaper explains. "The restriction to limit Metro style user experience participation to the user's default browser is rooted in preserving the Metro style user experience. Note that this limitation applies to all browsers, including Internet Explorer."
Bondy was uncertain whether Mozilla's future Firefox Metro-style enabled desktop browser would be available through the Microsoft Window Store "since it is not of Metro application type." Mozilla also may have to drop its ban on the use of Microsoft's ActiveX multimedia feature (a frequent security concern) because a Windows 8 requirement is to have ActiveX support included in apps, he noted.
Google affirmed to Computerworld author Gregg Kaizer that it is building a version of its Chrome browser to work with Windows 8, saying that "we're in the process of building a Metro version of Chrome along with improving desktop Chrome in Windows 8, such as adding enhanced touch support."
An Opera spokesperson told Computerworld that "we are currently looking into Windows 8" but would not confirm that it was building a browser to support it. An Opera Software blog in September showed screenshots of Opera running on the developer preview version of Windows 8.
H.264 Video Codec Support
Mozilla could be changing its mind on video codec support in Firefox. The organization might be looking at adding H.264 video codec support, for instance. Andreas Gal, director of research at Mozilla Corp., brought up this topic in a Mozilla developers platform discussion, although he noted that he doesn't have the sole authority to make such a decision.
Mozilla's reconsideration may stem, in part, from Google's actions. Apparently, Google never withdrew support for H.264 in its Chrome browser, even thought it promised to do so about a year ago. An Apple Insider article makes the claim that H.264 is still supported in Chrome. No reply from Google was received at press time to confirm whether that claim is true.
Google announced plans to drop H.264 support altogether in its Chrome browser in January. That move was a shot at MPEG LA, a group of patent-holding companies that includes members like Apple and Microsoft -- all having intellectual property associated with the H.264 video codec. MPEG LA had targeted Google's VP8 for legal action, asking its members to check if their patents were infringed by it.
Google's substitute for H.264 was its WebM project, which would support an open video codec based on Google's VP8. Mozilla and Opera both favored the VP8 and Ogg Theora codecs and did not support H.264. However, if Google did not drop H.264 support in Chrome, then that might explain Mozilla's change of heart on the issue.
Hardware vendors, independent software vendors and browser makers have to pay royalties if the patented H.264 technologies are used in their products. However, individual users aren't being charged for using H.264 technology to view Internet videos, which is an arrangement that MPEG LA stated (.PDF) would last through the life of MPEG LA's license.
Kurt Mackie is senior news producer for 1105 Media's Converge360 group.