Both Google and Mozilla are hard at work porting Chrome and Firefox to Windows 8, building Metro versions of their browsers. Microsoft, though, could block both browsers from running on Windows 8 tablets. It’s not clear yet that something Microsoft will do.
A month ago Mozilla was the first company to announce that it was developing a Metro-based browser to compete against Internet Explorer on Windows 8. As a first step, Mozilla said it would develop a “technology proof of concept” of the browser, to be launched in the second quarter of 2012, followed by alpha and beta versions in July through December.
Mashable reports that Google is working on a version of Chrome that will work on Metro as well. A spokesperson told the site: “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.”
There’s a chance, however, that neither Chrome or Firefox will be allowed to run on Windows 8 tablets. Gregg Keizer of Computeworld notes that Firefox will use the existing Gecko libraries to build the Metro version of Firefox. But he warns that the browser will not run on Windows on Arm (WOA), the version of Windows that will run on tablet. He writes:
If Mozilla’s assumptions are correct — that it will power Firefox Metro on Windows 8 via current Gecko libraries — its new browser would run only on Windows 8, not on WOA.
In Windows 8 PCs, Microsoft will allow browsers to be directly downloaded and installed, without having to go through the Windows Store. But on tablets, that’s not the case — all apps, including Metro browsers, will have to be downloaded via the Windows Store. Microsoft controls what apps are available in the Windows Store, and which aren’t allowed in. That means that theoretically Microsoft could block Chrome and Firefox (or any other browser) from being available through the store.
Microsoft couldn’t ban them on a whim, or it would potentially face legal action. But it could come up with a technical reason, such as not adhering to any of its standards. Some of those standards are laid out in a recently published white paper about browser development for Windows 8.
Mozilla recognizes that Firefox might not be available on Windows 8 tablets. Brian Bondy, a platform engineer with Mozilla, has this to say about that in his blog:
“The Firefox Metro enabled desktop browser can be, and will be included and packaged in the traditional way. I’m not certain if it will be allowed on the Windows store or not since it is not of Metro application type.”
When he says that it is “not of the Metro application type,” that doesn’t mean it’s not developed for Metro. It means, instead, that it can run either as a Metro app or a Desktop app.
Even if Firefox and Chrome are available on Windows 8 tablets, it’ll be tough for them to gain any market share there. Metro only allows the default browser to run. So if Internet Explorer is the default browser, no other browser will be allowed to run on Metro. To run another browser, you’ll have to make it the default, and then only it will be allowed to run.
Will Microsoft block Firefox and Chrome from running on Windows 8 tablets? That’s not at all clear, but it would be a mistake. Not allowing popular browsers to run on the tablet could cut down on its appeal for people. Microsoft tablets are far behind the iPad and Android tablets, and Microsoft needs to do everything it can to get people to buy Windows 8 tablets. Not allowing popular browsers to run on them would only cut into the potential market share.
Computerworld - A year after it pulled the plug on silent updates in Firefox 4, Mozilla said it will debut most of the behind-the-scenes feature by early next year.
Assuming Mozilla pulls off silent upgrading this time around, it would make Firefox only the second browser to take that route. Google’s Chrome has been the poster boy for automatic updates that remove the user from the equation and can’t be switched off.
Mozilla did not say it was copying Chrome — it’s denied doing so with other features — but the chairman of the Mozilla Foundation, Mitchell Baker, acknowledged what she called “update fatigue.”
“In the past we have been very careful to make sure people know something is changing with their Web browser before it changes,” said Baker, who heads the non-profit organization that oversees the Firefox-making Mozilla Corp. “Today people are telling us — loudly — that the notifications are irritating and that a silent update process is important.”
The difference between then and now, a Mozilla developer explained, is the rapid release schedule that upgrades Firefox every six weeks.
“Most users don’t want to think about software updates nor version numbers and now they are being forced to do so every six weeks,” said Brian Bondy, a Mozilla developer working on one component of silent updating, in a blog post last Friday.
According to Bondy and other information published on the Mozilla website, the current goal for most of the multi-part project is Firefox 10, slated to ship Jan. 31, 2012. Some pieces will appear in earlier and later editions, however.
When Firefox receives the feature, the browser will download the upgrade in the background, then install it the next time Firefox is restarted. Users will be reminded to install the upgrade 12 hours later if they haven’t restarted the browser before then.
Mozilla may sidestep the UAC (user account control) prompts in Windows Vista and Windows 7 by building its own Windows service for the silent upgrade mechanism. That will require users to okay the install one time only; all subsequent upgrades will not bother the user, said Bondy.
That’s a different tactic than the one used by Google’s Chrome, which avoids UAC prompts by installing itself into a different folder than “Program Files” on Windows.
Unlike Chrome, Firefox will let users switch off silent upgrading.
Mozilla began work on a security-patch-only silent update service for Firefox 4 in August 2010, but quickly abandoned the feature. Firefox 4, which launched in March 2011, was delayed several months as developers wrestled with numerous problems; that delay was one reason why Mozilla shifted Firefox to a faster release cadence.
Some of that work, however, was clearly recycled in the new project.
Last year, Mozilla developer Robert Strong had rejected the idea of mimicking Chrome to avoid UAC prompts, saying that Google’s approach was risky. “Chrome accomplishes [silent updates] in part by forcing the install of Chrome into the user’s profile which has a set of issues associated with it that we don’t want to have, so we aren’t taking that route,” Strong said at the time.
Strong leads the Mozilla team that’s again working on silent upgrading.
Even without a silent upgrade mechanism, Mozilla has been pulling most users along with each new edition. According to Web metrics firm Net Applications, Firefox 6 — which launched mid-August — made up over half of all copies of the browser in use last month. The “tail” of those still running Firefox 4 and Firefox 5 was relatively short, representing about 13% of all Mozilla browsers.
More information about Mozilla’s silent updating plans can be found on the company’s website.
Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld. Follow Gregg on Twitter at @gkeizer, on Google+ or subscribe to Gregg’s RSS feed . His e-mail address is firstname.lastname@example.org.
Read more about Browsers in Computerworld’s Browsers Topic Center.