Business Tech

Mozilla is building a number of features into the upcoming Firefox 3.7 browser--but the organization now has begun stewing over whether to introduce some of them in a significant update, as planned, or to rewrite some sooner for a variation of the current browser.

Programmer Benjamin Smedberg proposed the retrofit approach with a version called Lorentz on a Mozilla mailing list in late December. In the resulting discussion, developers and observers weighed the tactical advantages to each approach and wondered whether the quickening pace of Firefox development is ill-suited to browser users among businesses.

Firefox is based on a browser engine project called Gecko. The nearly complete (but somewhat tardy) Firefox 3.6 is built on Gecko 1.9.2, and Firefox 3.7 is set to use Gecko 1.9.3. The question afoot is whether to "backport" significant Gecko 1.9.3 features to 1.9.2 and release the new Lorentz version of Firefox based on it.

"With the [Lorentz] project branch, I believe we could go to beta in the middle of January and release in late March/early April," Smedberg said. In contrast, "doing a release from Mozilla-Central/1.9.3 presents a lot of schedule risk without matching reward."

One design change in question is the implementation of out-of-process plug-ins, which would move plug-ins such as Adobe Systems' Flash to a separate computing process--and a project in which Smedberg is involved. The work, the first phase of a Mozilla project called Electrolysis, is expected to improve stability; many browser crashes are the result of problems with Flash programs. Another feature he'd like is a less disruptive browser update process--a particularly relevant technology, given Mozilla's attempt to move to a more frequent release cycle.

Some at Mozilla would like to see a few new features added to the nearly final Firefox 3.6 rather than wait for a later, more substantial update.

(Credit: Mozilla)

Chris Blizzard, who runs Mozilla's developer relations, sounded supportive of the Lorentz plan in a mailing-list message. He added some features he'd like to implemented sooner rather than later, including faster Direct2D-based graphics for Windows machines, CSS transitions that can add pizazz to some graphic elements, and Web Sockets for communication between a browser and a server.

But, he added, delay is a risk of new features. "We need to make sure this train doesn't get too big, though, or it will stretch out into a pretty long release," Blizzard said. Indeed, that's what happened with Firefox 3.5, which began as a quick 3.1 update but arrived months later, as more features were added.

Added L. David Baron, "I have bad feelings about this plan, based on the last time we did this: Firefox 2.0 sucked resources away from the trunk [the development of new version of Gecko] and allowed it to become extremely unstable, and it look a long time to get things back together for Firefox 3."

Eventually, the Mozilla mailing-list discussion turned to how well corporate users are able to deal with a fast development cycle.

"The nature of the Web doesn't really lend itself to long-lived stable browser branches, IMHO," programmer Robert O'Callahan said. "A lot of the security issues we discover in the Web itself require proactive security measures such as UI [user interface] and architectural changes that one normally wouldn't apply to a 'stable branch.'"

John J. Barton, an IBM programmer involved with the Firebug extension to Firefox to aid Web developers, made the case for relatively rapid changes.

"IBM and our customers are all moving to faster development cycles," Barton wrote. "That's why I urge [the] Firefox team to continue to lead in that direction."

In its 15th month of public existence, Google's Chrome browser surpassed Safari for share of worldwide usage in December.

Chrome jumped from 3.9 percent to 4.6 percent of usage, according to statistics that analytics firm Net Applications publishes based on the 160 million monthly visitors to the network of Web sites using its services. Safari increased from 4.4 percent to 4.5 percent.

Chrome passes Safari for third place in browser usage in December.

(Credit: Net Applications)

Chrome's jump came as Google released the first beta version of its browser for Mac OS X and Linux computers. Previously only a developer-preview version was available.

As of last month, Google had been scheduled to graduate the Chrome 4.0 beta version to "stable" on January 12, but mention of that release date has now been removed from the Chromium development calendar. One possible hitch: the Mac beta version and the present Mac developer-preview version don't yet support one key feature of the newer 4.0 incarnation of Chrome: extensions. That means the feature, which lets people customize what the browser can do to some extent, has yet to receive widespread testing on Mac OS X machines.

Also according to Net Applications' statistics, Microsoft's Internet Explorer continued its steady slide, dropping from 63.6 percent to 62.7 percent usage. Most of IE's share loss has been picked up by No. 2 Firefox, but that open-source browser slipped from 24.7 percent to 24.6 percent from November to December.

Better news for Microsoft, and for Web developers who loathe supporting the IE 6 browser first released in 2001: IE 8 has almost edged the older browser aside as the top browser version in use.

IE 8 rose in usage from 19.3 percent to 20.9 percent from November to December, while IE 6 dropped from 22.1 percent to 21 percent.

After crushing Netscape in the first browser wars of the 1990s, Microsoft grew complacent. But the arrival of Firefox and growing usage of other browsers has re-energized the Internet Explorer team.

Mozilla won't make a 2009 deadline for releasing Firefox 3.6 and is giving itself more time to complete a major update, version 4.0.

The organization behind the open-source Web browser had predicted a final release of Firefox 3.6 in December 2009, but the Mozilla Web site now includes "ship Firefox 3.6" as a goal for the first quarter of 2010.

In addition, Firefox 4.0, which had been due in 2010, now is "aimed at late 2010 or early 2011," with a beta due in the summer of 2010, according to Mozilla.

Schedule delays are common in the software world, but browser development is furious these days with the arrival of Google's Chrome into the market, Apple helping to expand the frontiers of what the browser can do, Opera trying to dramatically speed up JavaScript execution and display performance, and Microsoft getting more ambitious again with Internet Explorer. "We've always been more quality-driven than time-driven, but we understand timing in the market matters to our users and our competitiveness," said Mike Shaver, Mozilla's vice president of engineering, in an October interview.

Mozilla, racing to release Firefox 3.6 by the end of the year, issued a fifth, and likely final, beta version of the new browser.

The open-source browser backer announced the new Firefox beta (download for Windows and Mac OS X) in a blog announcement Thursday.

Firefox 3.6 builds in a feature called Personas for customizing the browser's appearance, adds the File interface for better file management such as selecting what to upload, and, my personal favorite, placement of new tabs next to the ones that spawned them.

A total of 127 bugs were fixed since the fourth beta, but this time Mozilla didn't announce any new features. The first Firefox 3.6 beta arrived in October.

Mozilla had considered issuing its first Firefox 3.6 release candidate this week: "If we can go to build today or tomorrow, QA [quality assurance] will scrap Beta 5 and we'll release RC to the beta audience ASAP," the Mozilla meeting notes said.

Mozilla has updated its Firefox browser to patch three critical security holes.

Firefox 3.5.6 and 3.0.16 both fix earlier memory corruption issues. "We presume that with enough effort at least some of these could be exploited to run arbitrary code," the security advisory said.

In addition, the earlier version of Firefox 3.5 had two critical vulnerabilities in its technology for playing Ogg-format media, one with the liboggplay media library and one with the libtheora video library.

The patches are among 62 fixes in the new Firefox, software that's translated into dozens of languages and runs on multiple operating systems. Users of the OS/2 operating system will be delighted to know that problems with Firefox's full-screen mode and with print preview have been resolved.

"We strongly recommend that all Firefox users upgrade to this latest release," Mozilla said in a blog posting. By default, Firefox downloads updates automatically then prompts users to restart when it's ready; updates also can be retrieved through the "check for updates" menu option.

Mozilla plans to cease supporting Firefox 3.0 in January. Meanwhile, a significant update, Firefox 3.6, is due by the end of the year.

Correction 1:23 p.m. PST December 17: This story was corrected to note that it was the earlier versions of Firefox that suffered the vulnerabilities.

3D graphics became ordinary first in games, then in operating systems, and on Thursday, it took a significant step toward being built into Web browsers as well.

The Khronos Group, which oversees the OpenGL graphics interface, announced that its work with Mozilla to bring hardware-accelerated 3D graphics to the Web has reached draft standard form. The standard, called WebGL, lets programmers who use the Web's JavaScript language take advantage of the fact that video cards can handle 3D graphics with aplomb.

The group now wants commentary from Web developers and others who might be involved with WebGL so it can be finalized. "I anticipate us moving toward a spec that is not provisional, not merely a draft, in early 2010, the first quarter," said Arun Ranganathan, chairman of the WebGL working group and standards evangelist at Mozilla.

Internet Explorer remains the dominant browser in terms of usage, but all four of its main challengers--Mozilla's Firefox, Apple's Safari, Google's Chrome, and Opera Software's Opera--are working hard, sometimes in an informal alliance, to get ahead by advancing the Web state of the art.

WebGL fits into that effort, and not just academically. All four of those browser makers have endorsed WebGL, and developer test versions of Firefox, Safari, and Chrome have it built in. Microsoft declined to comment for this story beyond reiterating its general support for standards.

Ultimately, building 3D support into the Web could advance user interfaces of Web applications--including games, the popularity of which can be a powerful incentive for upgrading to the latest technology.

It's not clear exactly how it will play out, though, Ranganathan said. The arrival of Canvas, an advanced 2D interface for browsers, has led to a blossoming of graphics work, and he expects a similar change with 3D graphics.

But don't hold your breath for Web-based first-person shooters that rival native applications. First, even if 3D is accelerated, there are plenty of other processing and user interface constraints on Web applications. Second, even after WebGL is standardized, it must be built into browsers, people must upgrade to those new versions, and programmers must learn how to support the technology.

WebGL isn't the only 3D Web work under way. Google has its own O3D project, which currently is a browser plug-in but that the company also is building directly into Chrome.

O3D is a higher-level interface, though, not a direct competitor. Details are technical, but O3D uses a retained mode approach to WebGL's immediate mode interfaces.

And of course, a decade ago there was VRML--virtual reality modeling language, a file format rather than interface. A VRML successor called X3D, though, can actually make use of WebGL, and indeed a project called X3dom aims to do just that.

Mozilla is wrapping up work on its first version of Firefox for mobile phones, an important step in bringing the second most popular PC browser to an area where a rival project holds more influence.

"Our goal is to have a release candidate next week," said Jay Sullivan, Mozilla's vice president of mobile. "If things go smoothly, we'll have a (final) version out in the next few weeks," with the debut planned for this year, he added.

Mozilla has been a leader in advancing the Web state of the art. But when it comes to the mobile phones, where the power of a new generation of hardware has transformed browsers from primitive afterthoughts to useful tools, Firefox has been missing in action.

Instead, an open-source project called WebKit powers the browser on the higher-end mobile phones du jour--Apple's iPhone, the Palm Pre, and Motorola's Droid and other models running Google's Android operating system, with BlackBerry headed that direction, too.

In contrast, the first mobile Firefox version will run on Nokia's powerful but relatively obscure new N900, a $569 hybrid computer and mobile phone that uses Nokia's Linux-based Maemo operating system. A Windows Mobile version of Firefox is set to arrive next year, and Mozilla has begun working on an Android version now that Google released a native developer kit.

Firefox has one big thing going for it, though: it's a close relative of the PC-based browser that today is used by about a quarter of people on the Web.

The link extends beyond brand familiarity. For one thing, mobile Firefox is based on the same code as the present Firefox 3.6--also a beta version due to finished by the end of 2009. For another, through a Mozilla service and browser plug-in called Weave, mobile Firefox synchronizes bookmarks, passwords, and even open tabs with the desktop version of the browser.

In addition, Firefox for the N900 can run many Firefox extensions--AdBlock Plus among the 30 or so now available. Sullivan recommends updating their interfaces for the small devices, though.

Nokia partnership
Mozilla has been working closely with Nokia to develop Firefox on its N900 handset. It already ships with a lighter-weight browser that uses the same Gecko code base as Firefox, but the full Firefox mobile version--a project code-named Fennec--is more powerful.

"You want to put the desktop experience into a pocket-sized device," said Ari Jaaksi, vice president of Maemo devices. "What do people use on the desktop? Firefox."

However, Firefox won't ship with the device, at least initially. The company is open to the idea of including it in the next version of the operating system, due in the second half of 2010, Jaaksi said. Mozilla, meanwhile, is comfortable with the idea of people having to actively download the browser, the most common way Firefox has been distributed on PCs.

The N900 is available as an unlocked device through various retail channels, but Nokia doesn't yet have any partnerships in the United States with wireless service carriers who might help bring the N900 to a broader market. It's a relatively powerful device with a 600MHz processor and 3D graphics hardware--enough oomph to run Adobe Flash on Web pages today. Its price may seem high, but bear in mind that unlocked devices don't get a subsidy by carriers that expect to see their up-front payment returned over months of subscription payments.

Nokia's N900 will be the first device that runs the mobile version of Firefox.

(Credit: Nokia)

So does Firefox require this level or horsepower?

"We need pretty high-end stuff to make the Web great," Sullivan said, but not so high-end that the N900 is the only handset to fit the bill. "Everything now on the mid- to high-end is fine."

WebKit has intercepted the newer generation of smartphones. Through the wonders of Moore's Law, new devices get steadily more processing power and memory. So aiming for today's top-end phones can mean software will work on tomorrow's mainstream models.

The N900 is at the top end of the range, but Firefox runs elsewhere, too. The Windows Mobile version of Fennec is in alpha testing now, lagging the Maemo version by about three or four months, Sullivan said. Mozilla plans to release it in final form in the first half of 2010, he said.

Firefox: like an operating system?
Mozilla has a lot of plans for mobile Firefox that, to some extent, put it in opposition with Nokia. The N900 is aimed in part at programmers who want to low-level control over a device through its Linux operating system. But Firefox--like Google's Chrome--is assuming the role of a general-purpose foundation for running programs.

"We're almost an operating system," Sullivan said.

Several features support the direction. Built into Firefox now is geolocation, which lets a Web application tap into the phone's services to figure out where a user is and, for example, show a map of the nearest pizza shops. Also included is support for orientation detection, important for games, and offline data storage, important for a variety of programming needs.

There's more on the way in 2010, Sullivan said:

• Support for multitouch displays for a more sophisticated user interface.

• Support for haptic feedback, such as the phone vibrating when a virtual keyboard key is tapped.

• The ability to control a camera.

• Support for Electrolysis, Mozilla's project to split tasks such as the user interface, tabs, and plug-ins into separate processes. That improves stability and performance, he said.

• Support for JetPack, Mozilla's next-generation extensions system.

S• Integration of the Weave synchronization software so it's no longer a plug-in.

• Support for WebGL, an interface to provide browsers with accelerated 3D graphics.

• Faster execution of JavaScript programs that are common and increasingly powerful on the Web.

Applications that run natively on a device--whether directly on the hardware as in the case of the iPhone or on the Java-derived layer called Dalvik on Android--are an important area of mobile development today. But the Palm Pre uses a browser-based application design.

"It's the right model. It's not there yet," Sullivan said of Web-based programs. Today programmers must create separate versions of applications for BlackBerry, Nokia's Symbian, Android, the iPhone, and other mobile phones.

But that profusion will be replaced by the universality of the Web, he predicted.

"In three years," Sullivan said, "80 percent of those applications are going to be Web-based."

Mozilla, determined to release Firefox 3.6 before year's end, is also determined to squeeze as many features as possible into the new browser.

The latest example: support for the File interface that adds more sophistication to uploading and some other chores.

Support for the feature is one of the 133 changes that arrived in Firefox 3.6 beta 4, which the Mozilla project released Thursday for Windows, Mac, and Linux.

The File API (application programming interface), a draft standard at the World Wide Web consortium, lets browsers handle files better. Among its abilities are uploading multiple files at once, showing thumbnail previews of images that have been selected for upload, breaking a long video upload up into chunks to protect against network interruption problems, and integrating with drag-and-drop Web applications.

While many software projects use beta testing periods to shake down their code, Mozilla isn't afraid to add new features as it goes. That can mean new ideas arrive sooner, of course, but it also can delay the completion date of the new version. What was to have been a quick Firefox 3.1 release was pushed back months as new features were added and the version ultimately was renamed Firefox 3.5.

For those who want to dig into the File interface, Mozilla offers a Web developer guide to using it.

The beta-testing periods aren't just important for debugging Firefox itself. New versions often don't work with older add-ons that people install to customize the browser, so beta testing gives some time for programmers to update those add-ons. Mike Belzner, Mozilla's director of Firefox, said 70 percent of add-ons are now compatible with Firefox 3.6.

Sometimes it's the little things that count.

The most prominent feature of Firefox 3.6 is Personas, which let you reskin the browser with thousands of different looks. But my single favorite change is a subtler change to the open-source browser's user interface.

Specifically, when you open a link in a new tab, it appears immediately to the right of the active tab. Before, the new tabs would appear to the far right of the strip of tabs.

Yup, that's it. For those of us who spend hours a day in a browser, though, the new tab behavior helps group related tasks together. I constantly shuffle among dozens of tabs, and the new approach automatically brings some organization to my cluttered life.

However, I know it's not everybody's favorite browser behavior. So along with explaining why I like it, I'll also take some potshots and share instructions on how to get the old way back.

Why it's better
The more things I do with a browser--and the number has increased steadily for years now--the more important it becomes to be able to find different tasks amid the chaos. Microsoft and Apple understand this, as evidenced by the new taskbar features in Windows 7 and dock expose in Mac OS X 10.6, aka Snow Leopard. Those features make it easier to pluck out the one window you need from among the many you may have open.

There's a pattern to how I spawn the dozens of tabs I use as a day progresses. On a variety of pages--Gmail, Google Reader, Yahoo Finance, somebody's blog post--I'll encounter a host of links to other pages. I'll middle-click my mouse button to open interesting pages as background tabs, then use Ctrl-Tab to switch to the new pages when I'm ready. I repeat this pattern many times a day.

With the old behavior, each tab appeared to the far right of the tab strip. That's fine when getting started, but when I've moved halfway across the list and want to open another batch, I want the new ones--call them children--to open next to their parent tab. When I go away and come back, or when I lose place juggling tasks, it's easier to find my bearings again.

It's like being in a library. When you're in the European history section, you don't want to find books on rewiring your house and on vegetarian cooking.

As a longtime Firefox user, I didn't realize tab positioning could be better. When I started using Google's Chrome, which introduced the new tab behavior to me, the scales were lifted from my eyes. I immediately could get to the next tab with a quick press of Ctrl-Tab on the keyboard rather than have to use the mouse to click over to the far end of the list. I use both browsers daily, but until the Firefox 3.6 beta arrived, the new-tab position had become a sore point for me when in Firefox.

The change is actually a big deal in a couple ways. First, even seemingly minor changes in software can be disruptive. Old habits die hard, and computer users wrestling with constant change can get angry when more is foisted upon them.

Second, though, browsers are assuming an ever greater role in what people do in their personal and professional lives, and keeping one's bearings is commensurately important. That's especially true for those people for whom a gaggle of browser tabs represents a collection of chores going on in parallel.

Internet Explorer 8 categorizes related tabs by color.

(Credit: Screenshot by Stephen Shankland/CNET)

How the competition handles it
Tabs are now universal among browsers, but new-tab behavior isn't. Firefox and Chrome handle it the way I like best, but how do others tackle the issue?

First, let's look at Internet Explorer 8. Microsoft showed it understands some of the challenges of tab management in its latest version of its browser by coloring child tabs the same hue as their parents, but I have a gripe with how it works. Specifically, although child tabs get the same color as their parents for easy grouping and arrive to the right, grandchild tabs are the same color as child tabs. Similarly, grandchild tabs appear to the far right of the whole group of child tabs.

In my mind, I consider grandchild tabs a separate group from the child tabs. But with IE, grandchildren get the same color and position treatment as children. The only way to get a new color is to start a fresh empty tab There's no easy way to give grandchildren a new color without causing some confusion, though--should the child be the same color as the original parent or change color to be grouped with the grandchildren?

Next is Opera, which gives users a choice. By default, it opens new tabs to the far right, which I don't like, but in the Advanced|Tabs section of the preferences dialog box, you can check "Open new tab next to active." Huzzah!

There's a subtle change here I don't care for, though. Tabs always appear immediately to the right of the active tab. I'd rather have all one tab's children appear in sequence to the right. For example, if a parent tab is in position 1, then the first child would be in position 2, the second in position 3, and the third in position 4. Opening three child tabs in Opera leaves the parent in position 1, the third child in position 2, the second child in position 3, and the first child in position 4.

Last, there's Safari. It does it the old way I loathe with no option to change. Too bad.

Firefox can show thumbnail previews of new tabs, but I find them hard to recognize in front of busy Web pages.

(Credit: Screenshot by Stephen Shankland/CNET)

Why it's not enough
Most browser makers are excited about the fact that their software is subsuming more and more computing tasks that previously ran on computer operating systems. But as browsers inherit this central importance, they also inherit some of the hassles.

The new tab positioning behavior in Firefox is a step in the right direction, but there's more that needs to be done. Moving from one tab to a related adjacent one, whether through a keyboard command or mouse clicking, is a minor change. But things get harder when you need to switch from one group of tabs to the next.

There's work under way here. Opera is perhaps the leader with the ability to show thumbnails as you use Ctrl-Tab to cycle your list of open tabs.

Firefox has been noodling with the approach too. It tried then dropped tab thumbnail previews earlier, but the technology is still present. Using the about:config system for tweaking the browser (more on this later), you can change the "browser.ctrlTab.previews" setting to "true."

But for reasons that aren't clear to me, I don't find this effective either in Firefox or Opera. Perhaps I haven't used it enough, or the thumbnails are too small to be immediately recognizable, or they're just hard to see against the noisy background. There's a good reason that Apple dims the background most of the way to black when using Expose.

Aero Peek in Windows 7 lets the task bar show a glimpse of Firefox and IE tabs.

(Credit: Screenshot by Seth Rosenblatt/CNET)

Windows itself is helping, too. The new taskbar in Windows 7 can show individual tabs, once browsers support the feature. It's in Internet Explorer 8, and it's in the new Firefox 3.6 beta.

Add-ons such as Firefox Showcase can further tweak Firefox. (Indeed, for a wealth of options, check Mashable's handy Firefox tab management guide.)

More interesting to me, though, is work under way to expand Firefox's "awesome bar" abilities. Today, typing in it opens Web pages and retrieves ones you've already visited or bookmarked. In the future, it could be able to move you to another open tab, too. I'm a keyboard guy, so particularly appreciate this idea.

You can get a taste of the idea now. If you've enabled the "browser.ctrlTab.previews" option, hitting Ctrl-Shift-Tab will not only show you thumbnail previews, but will put a cursor in a search box.

Typing the letters of the Web page name will winnow down the thumbnails. For example, typing "netap" will cull my open tabs so only Net Applications and NetApp show. If you have a bunch of similar tabs all open, this might not help much, of course.

However, the feature only works with the tabs of one browser window, so if you can't use it to search among other browser instances.

How to get the old way back
Perhaps I've convinced you that the new approach is better. But perhaps not--in which case I encourage you to share your thoughts in the comments so people will hear more than my opinion.

For those who don't like the new tab positions, you can revert to the old method.

To get the old style back for new tab position, use Firefox's about:config system.

(Credit: Screenshot by Stephen Shankland/CNET)

First type "about:config" in the Firefox address bar. You'll get a warning that you're tinkering with Firefox's innards and you should be careful, but this isn't brain surgery, so don't be frightened. Click the "I'll be careful, I promise" button, and you'll see a big list of all the browser settings that can be tweaked.

Next, in the text box labeled "Filter:", type "tabs.insertRelatedAfterCurrent"; you should see just one entry below. In the column marked "Value," double-click on the word "true" to change it to "false." You're done.

But I'd encourage you to at least give the new way a try. If you don't like it, you can always change back.