Firefox Metro hits Windows 8 with a very early, very buggy beta

Microsoft may have told app developers "Don’t call it Metro," but the latest version of Mozilla's browser for Windows 8 is called the "Firefox Metro Preview." The name is fitting in all senses.

It’s fitting because Mozilla has adopted the used-to-be-called-Metro design style with an attractive overhaul of the browser’s user interface. This is something Google did not do with Chrome. While there is a version of Chrome for Metro, it looks almost exactly like the desktop version, for better or worse.

The name "Firefox Metro Preview" is also fitting because "preview," if anything, is a polite word for this early state of the application. While both Microsoft and Google have Metro-style browsers in functional shape, Mozilla’s current schedule will keep the Metro version of its browser in beta for some time after the Windows 8 release on Oct. 26.

I installed the Firefox Metro Preview for Windows 8 RTM today on a Samsung Series 7 tablet with a 1.6GHz Intel Core i5 processor, 4GB of RAM, and an SSD drive. It’s probably too early to run benchmarks on the browser—but I did it anyway. Firefox actually beat IE10 in the Google Octane JavaScript benchmark, but lost in SunSpider, and simply could not complete the Peacekeeper HTML5 test.

The benchmarks show some promise, and the browser's existing features work pretty well. Everything it can do, it does quickly and smoothly. But there are lots of missing pieces, as noted by Firefox developer Brian Bondy in his blog. There is no panning and zooming. Scrolling is possible with touch, and a keyboard, but not with a mouse scroll wheel.

Flash and add-ons are both disabled for now. "Although we have plans for Flash support, the preview currently has it disabled," Bondy wrote. "You can add support for windowless plugins by setting plugin.disable to false in about:config. As previously mentioned, for the Metro environment only, even in the initial release, we will not have add-ons enabled. We will eventually add support for add-ons through the add-on SDK."

I experienced an odd bug myself that seems to be localized to my home office in Massachusetts. I cannot copy text in Firefox and paste it into a second application. I can copy and paste from another application into Firefox, but not vice versa. I tried both on the tablet and in a virtual machine, and even tried reinstalling Firefox, but am still having the problem.

My colleagues Andrew Cunningham and Sean Gallagher both tested it out and found copying and pasting does work on their machines. I won’t rule out operator error—whatever is causing my own problem, I am sure the answer lies somewhere deep within the Windows Event Viewer.

Metro Metro Metro

The Firefox Metro Preview is in the latest nightly build of Firefox version 18 (download link), which is scheduled for release Jan. 8, 2013 (the current stable version is 15). You can install both Firefox 15 and 18 side-by-side on Windows 8—Firefox 18 will simply be called "Nightly." The difference is that Firefox 18 includes both the desktop and Metro versions, while 15 includes only the desktop one. If you set Nightly as the default browser, and then access it from the Start Screen, it’ll load the Metro version. (Clarification: The build that includes Firefox Metro Preview is in a branch from Mozilla's normal nightly builds. The build with Firefox Metro will be merged with the main development version sometime in the next three months.)

When you open Firefox Metro, you'll see bookmarks on the left, recent pages in the middle, and downloads on the right. There is a single box at the top to type in a Web search or a URL, unlike the desktop version of Firefox which has separate boxes.

Interface-wise, it’s much more similar to IE10’s Metro version than Chrome’s. That means buttons and menus are optimized for touch, with bigger surface areas to accommodate the use of fingers instead of a mouse. But there are fewer options. There seems to be no way to have an always-present bookmarks bar like there is in Chrome, for example.

Webpages are displayed full-screen by default. If you swipe in from the top (or right-click at the top with a mouse) you reveal the URL/search bar and a plus sign for opening a new tab. If you swipe from the top or right-click a second time, the view expands to include open tabs:

There is an option to always show all tabs, instead of having to swipe down to show them. There are also obvious ways to bookmark pages or pin them to your Start Screen. The best way to easily access your bookmarks is to start a new tab page, which by default lists your bookmarks, recent pages, and downloads. There is not yet an option for creating new bookmark folders.

One handy feature lets you share the URL of whatever webpage you’re viewing by swiping in from the right to bring up the Windows 8 share contract. That lets you e-mail the URL or share the link via Facebook, Twitter, or LinkedIn, all without leaving Firefox.

Mozilla's sync service for syncing bookmarks and other data across devices is also enabled. But I haven't been able to download synced bookmarks, even though Firefox Metro claims it's completed the sync operation.

Benchmarks

On to the benchmarks! I attempted four tests, the three mentioned above (SunSpider, Google Octane, and Peacekeeper), and a Microsoft HTML5 test known as Chalkboard. All were performed on the Samsung Windows 8 tablet.

Chalkboard seems to be a test that only IE can perform well. While IE10 completed the test in 8.26 seconds, it took Firefox Metro 757.88 seconds (12.63 minutes), and Chrome simply couldn’t finish it at all.

Even if we discount this test, IE10 feels fast in Windows 8 and it outperformed the competition in SunSpider. While IE10 completed the SunSpider JavaScript benchmark in 302.8ms, Chrome took 413.6ms and the Nightly Firefox took 459.2ms.

Firefox Metro’s best result came in Google Octane, where it scored 4,928, much better than IE10’s 1,465. Chrome hit 7,056. The results were so disparate that I ran the tests again, and got nearly identical results.

With PeaceKeeper, Firefox Metro wasn’t able to finish the test at all, on either the tablet or in a VM. Chrome (on the tablet) scored 1,998, better than IE10’s score of 1,071.

The results just stated include the Nightly build of Firefox 18. Since we were comparing the browser to stable versions of Chrome and IE10, it’s only fair to run the same tests on Firefox 15 as well.

The results were better and worse. Firefox 15 on the Windows 8 tablet did SunSpider in 345.4ms, scored 4,653 on Google Octane, and did the Microsoft ChalkBoard test in 279.78 seconds. Firefox 15 was able to finish PeaceKeeper, coming up with a score of 1,307.

A late start. Does it matter?

Firefox obviously got a slow start in having a Metro-ready browser for the Oct. 26 launch of Windows 8. Internet Explorer 10 is ready, of course. Chrome is too, in a sense, because Google didn't change the user interface much, perhaps betting that most Windows 8 users will be using traditional mice-and-keyboard setups instead of tablets. Mozilla has a long road ahead, as evidenced by the state of this first version and its target date of January for a Firefox 18 release.

Firefox product manager Asa Dotzler writes in his blog that "Over the coming weeks and months, we’ll be adding more features, tightening up Windows integration, improving performance and responsiveness, and finishing up all the necessary work to deliver a first class Firefox experience for Windows 8."

The different states of Firefox and Chrome on Metro could indicate that the makers of the two browsers have very different strategies for Windows 8, or just that they are on extremely different development cycles. I downloaded the latest development build of Chrome and found its Metro interface to still be largely unchanged from its desktop version.

Firefox Metro, for all its early problems, is thus a lot closer to being a touch-ready browser on Windows 8 than Chrome. At the same time, the Metro version of Chrome is more stable than the Metro version of Firefox, precisely because it's generally the same as the desktop version. Google may have the more attractive browser than Firefox for Windows 8 users who use Metro with a mouse and keyboard. But for those who buy Windows 8 tablets, Firefox looks like it will be the better option once all its various bugs are fixed and its missing features restored.

Promoted Comments

I seem to remember reading something about Win 8 in metro mode not allowing applications to modify/run their own code. Which ruled out a good JIT implementation. Of course IE had a backdoor around this.

Is that really the case or not?

Microsoft has made a special case to allow browsers to run natively in the Metro interface on Intel processors. These are "normal" Windows 8 machines. However Microsoft for Windows 8 RT, which runs only on ARM hardware, has disallowed 3rd party access to the native APIs - thus preventing a Firefox port. This is something about which Mozilla has already voiced their objection.

I seem to remember reading something about Win 8 in metro mode not allowing applications to modify/run their own code. Which ruled out a good JIT implementation. Of course IE had a backdoor around this.

I seem to remember reading something about Win 8 in metro mode not allowing applications to modify/run their own code. Which ruled out a good JIT implementation. Of course IE had a backdoor around this.

Is that really the case or not?

This only applies to Windows RT. Windows 8 has an exception permitting third party browsers equivalent access as IE10.

I seem to remember reading something about Win 8 in metro mode not allowing applications to modify/run their own code. Which ruled out a good JIT implementation. Of course IE had a backdoor around this.

Is that really the case or not?

Microsoft has made a special case to allow browsers to run natively in the Metro interface on Intel processors. These are "normal" Windows 8 machines. However Microsoft for Windows 8 RT, which runs only on ARM hardware, has disallowed 3rd party access to the native APIs - thus preventing a Firefox port. This is something about which Mozilla has already voiced their objection.

Mozilla did a fantastic job of making it fit into the Metro Modern design even with sticking to the Australis theme. Much better than Google has done so far with Modern Chrome which is all of nothing. It's just the desktop Chrome interface in full-screen.

The different states of Firefox and Chrome on Metro could indicate that the makers of the two browsers have very different strategies for Windows 8, or just that they are on extremely different development cycles.

I think it indicates just how clean Chrome's source code is compared to FireFox.

Remember, Apple poached one of mozilla's best developers (David Hyatt) to run their Safari team and apparently he was one of the people who decided to base Safari on khtml* instead of gecko* — claiming that khtml's inferior web page rendering at the time was more than made up for by the fact it has nice clean source code.

* khtml is the rendering engine that WebKit/Google Chrome is based on, and gecko is the rendering engine in FireFox

So what about all the people who aren't going to use a touch screen device, do they have to suffer through all these superfluous design choices that actually make your experience more difficult and unenjoyable when not using a touch screen?

Is there now going to be another whole separate version of FF? 18 contains both so is this the new norm?

Microsoft is trying to make another OS area within an OS but instead a locked down version of which it is the gatekeeper and can charge a fee for everything in it and deny anyone it wants. Now to serve Microsoft's greed and monopoly building Mozilla and others have to build more versions and stress their resources even further. FF crashed while making this comment, as you can see it doesn't need more things vying for its attention.

The different states of Firefox and Chrome on Metro could indicate that the makers of the two browsers have very different strategies for Windows 8, or just that they are on extremely different development cycles.

I think it indicates just how clean Chrome's source code is compared to FireFox.

Look at the Chrome interface for Metro. They haven't done anything to it but make it run full screen, otherwise it's exactly the same as the old interface. They haven't even changed anything to allow for touch or attempted to match MS' new interface guidelines.

So what about all the people who aren't going to use a touch screen device, do they have to suffer through all these superfluous design choices that actually make your experience more difficult and unenjoyable when not using a touch screen?

You keep using the desktop version, just like you're doing now. You're not forced to use the Metro version.

Microsoft has made a special case to allow browsers to run natively in the Metro interface on Intel processors. These are "normal" Windows 8 machines. However Microsoft for Windows 8 RT, which runs only on ARM hardware, has disallowed 3rd party access to the native APIs - thus preventing a Firefox port. This is something about which Mozilla has already voiced their objection.

Look at the Chrome interface for Metro. They haven't done anything to it but make it run full screen, otherwise it's exactly the same as the old interface. They haven't even changed anything to allow for touch or attempted to match MS' new interface guidelines.

I'm a software developer, trust me when I say it wasn't that easy.

The tab bar and back/forward buttons at the top of the screen are, at most, a few days of work. Porting the rendering engine itself to metro is the hard part, and both Chrome and FireFox would have run into the same challenges.

There would have been bugs in chrome, but they were easy to fix so nobody ever saw them.

The different states of Firefox and Chrome on Metro could indicate that the makers of the two browsers have very different strategies for Windows 8, or just that they are on extremely different development cycles.

I think it indicates just how clean Chrome's source code is compared to FireFox.

The different states of Firefox and Chrome on Metro could indicate that the makers of the two browsers have very different strategies for Windows 8, or just that they are on extremely different development cycles.

I think it indicates just how clean Chrome's source code is compared to FireFox.

Wait, what ?

For firefox they print out the source code, get their cheetos fingers all over the pages and then box it up and mail it to India for some guy to type into the computer and compile. The result is firefox 15.0.1

The tab bar and back/forward buttons at the top of the screen are, at most, a few days of work. Porting the rendering engine itself to metro is the hard part, and both Chrome and FireFox would have run into the same challenges.

That's just it, Chrome didn't port anything, because it's not strictly necessary *to* port anything. That's what the browser exception was for, was to permit the software to have access to both the Metro and the legacy APIs simultaneously. Chrome is leveraging just enough Metro APIs to make it work in that environment, while the Firefox team is rearchitecting the entire thing in order to make Firefox a first-class Metro app. It's my guess that the FF team's ultimate goal is to have something they can slot immediately into WinRT if MS ever comes to their senses about that, while the Chrome team has done just enough to make it work in Metro as the default browser on Win8 and doesn't care about WinRT.

It's funny, I could take or leave any of the major three browsers on the desktop. They're all of very similar, high quality. I happen to use FF because it's what I always have.

In the mobile space, though, Firefox has really got its shit together. The latest Android beta on the Nexus 7 is a really fantastic browser, full of interesting and useful little touches. If the WinRT version can settle on that kind of quality I won't have any qualms planting a flag in the Mozilla camp there either.

It's funny, I could take or leave any of the major three browsers on the desktop. They're all of very similar, high quality. I happen to use FF because it's what I always have.

In the mobile space, though, Firefox has really got its shit together. The latest Android beta on the Nexus 7 is a really fantastic browser, full of interesting and useful little touches. If the WinRT version can settle on that kind of quality I won't have any qualms planting a flag in the Mozilla camp there either.

On the Nexus 7 the UI is reasonable, but on a phone it's annoying.. everything is at the top of the screen, the way I hold my mobile phone my thumb is typically near the bottom. So, a UI like Opera Mobile or Safari is great. But Firefox and Chrome on a mobile phone is an annoying exercise to get my thumb or a finger from my other hand to reach the top of the screen. It gets old fast.

Also, Firefox Mobile renders in 16bit colour. Colour banding everywhere, on some sites it is horrible.

It's funny, I could take or leave any of the major three browsers on the desktop. They're all of very similar, high quality. I happen to use FF because it's what I always have.

In the mobile space, though, Firefox has really got its shit together. The latest Android beta on the Nexus 7 is a really fantastic browser, full of interesting and useful little touches. If the WinRT version can settle on that kind of quality I won't have any qualms planting a flag in the Mozilla camp there either.

The stable, non-beta version of Firefox for Android works on the Nexus 7 now. I just downloaded it, it looks nice.

So what about all the people who aren't going to use a touch screen device, do they have to suffer through all these superfluous design choices that actually make your experience more difficult and unenjoyable when not using a touch screen?

Is there now going to be another whole separate version of FF? 18 contains both so is this the new norm?

Microsoft is trying to make another OS area within an OS but instead a locked down version of which it is the gatekeeper and can charge a fee for everything in it and deny anyone it wants. Now to serve Microsoft's greed and monopoly building Mozilla and others have to build more versions and stress their resources even further. FF crashed while making this comment, as you can see it doesn't need more things vying for its attention.

Microsoft wants all platforms (desktop, mobile, gaming) to have the same interface and OS, they are trying to force touch onto laptop makers too, wouldn't be surprised if there are 24" touch monitors for home use soon too. This is one of the reasons people don't want Windows 8, it's going to be a mess, more locked down, more expensive devices and less consumer friendly.

So what about all the people who aren't going to use a touch screen device, do they have to suffer through all these superfluous design choices that actually make your experience more difficult and unenjoyable when not using a touch screen?

You keep using the desktop version, just like you're doing now. You're not forced to use the Metro version.

If that's the case, why can't you turn off the awful Metro start screen for desktop users?

So what about all the people who aren't going to use a touch screen device, do they have to suffer through all these superfluous design choices that actually make your experience more difficult and unenjoyable when not using a touch screen?

You keep using the desktop version, just like you're doing now. You're not forced to use the Metro version.

If that's the case, why can't you turn off the awful Metro start screen for desktop users?

Easy, once it starts up, click the desktop tile. Once the desktop has been selected hitting the start button will switch between the start screen and the desktop, just like the start button. Problem solved.

I'm presently running Firefox 15.01 from my Win8x64 desktop without problems, Flash included. Having it run from the Metro GUI is completely unimportant to me, as I consider that to merely be a "start page" instead of a "start menu." IIRC, when I first tried to cut & paste inside FF 15.x running under Win7x64--I couldn't, and Mozilla says the function is disabled by default in the browser. The instructions for enabling cut & paste inside FF 15 are very simple and I used them to activate the feature--but darned if I can recall what they are at the moment (sheepish grin.) You may be talking about something a bit different, however.

Edit: Kind of funny--I booted into Win8x64 RP and ran FF 15.01 and loaded the ars site and as I was scrolling through the forum, FF crashed... I sent Mozilla the reports.

Chrome dev channel appears to be faking things by switching to windowed/desktop mode behind the scenes while presenting the user with a faux Metro UI treatment. The only "native" Metro support is the Chrome tile (glorified shortcut) that makes the charade work.

The tab bar and back/forward buttons at the top of the screen are, at most, a few days of work. Porting the rendering engine itself to metro is the hard part

The rendering engines themselves are already very portable cross-platform code. Porting those to Metro took very little work compared to porting all the system-integration bits (OS event handling, possibly font API bits, graphics API shims, and so forth).

And that's where Chrome just took the easy way out and didn't do the system-integration work for Windows 8 Metro and its touch interface.