The Download Blog

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.

Mozilla may have released the first beta of Firefox 3.6 nearly two months late, but the organization believes the final version still will arrive on schedule before the end of the year.

The Mozilla wiki page on version 3.6, code-named Namoroka, listed early September for the scheduled release of the first beta, but it actually arrived October 30. Despite that, Mike Shaver, vice president of engineering, said Mozilla wants to release the browser before the holidays and is sticking by the overall schedule for the open-source Web browser.

"We're still looking at a release candidate in November and (final) release in December at this point," Shaver said in a Tuesday interview.

That means Mozilla has a compressed schedule for producing the final version, but Shaver said coders are working hard. "We're not going to coast into it," he said. "We're going to continue shipping beta updates aggressively."

Those involved in open-source projects, with different motivations and pressures than those in the traditional proprietary software industry, sometimes have an attitude of "we'll ship it when it's done." Mozilla, though, recognizes that time matters even for an open-source project.

"We've always been more quality-driven than time-driven," Shaver said. "But we understand timing in the market matters to our users and our competitiveness."

Those keen to try out Mozilla's latest browser--and its new process to update the software more frequently--now can try Firefox 3.6 beta 1 for Windows, Mac, or Linux.

Among the features in the new version, according to Mike Beltzner, Mozilla's director of Firefox, and Mozilla evangelist Chris Blizzard:

• Personas, which lets people customize the browser appearance. Personas has been available as an add-on, so there are plenty of Personas skins to choose from.

• Faster execution of Web-based JavaScript programs, better browser responsiveness, and faster startup time. Mozilla has been working on JavaScript performance for many months, but the urgency of that and other performance improvements increased with the arrival of Google's Chrome browser.

• The ability to drag and drop files from the computer to the browser. This is useful for uploading files to Web sites, as will a feature not in the beta but planned for the final version, support for the multiple-file input tag so more than one file can be added in Web forms.

• Expanded support for geolocation technology so it can provide a Web site with an approximate physical address of the user, not just latitude-longitude coordinates.

• The ability to detect the computer's orientation for machines that offer accelerometer support.

• Video built into Web pages with the HTML5 "video" tag now can be viewed full-screen.

Mozilla also released a full list of Firefox changes developers should know about with more details.

Firefox is at the vanguard of the second generation of browser wars. Although it competes with Google's Chrome, Apple's Safari, and Opera, all those browsers are also allied in a way against Microsoft's Internet Explorer, which though dominant is relatively slow at some tasks and only now complying more fully with Web page standards of yesteryear. The rivals, meanwhile, are pushing ahead with new features in HTML5 in development right now.

Mozilla released the alpha version of Firefox 3.6, code-named Namoroka, in August.

The organization plans to release the final version by the end of the year, with Firefox 3.7 in the first half of 2010 and Firefox 4.0 in about a year.

One complication of the upgrade is compatibility of add-ons that extend Firefox's features; the new browser version makes some changes. Mozilla is debating whether to release Firefox 3.6 as a minor update automatically distributed to 3.5 users or as a major update that requires those users to actively retrieve it.

One major element of Firefox 4.0 is a new add-on technology called Jetpack that eases this compatibility problem.

Mozilla hopes to classify the upcoming Firefox 3.6 as a minor update, a move that may sound inconsequential but that in fact might have significant repercussions with Firefox users and the speed the open-source browser is developed.

Mike Beltzner, Mozilla's director of Firefox, in a mailing list discussion that he'd like to call the new version a minor release "to quickly migrate our user base to Firefox 3.6." Minor releases in the past typically have been steps from, for example, 3.5.3 to 3.5.4, but Mozilla is trying to speed up more significant changes and not just fixes for bugs and security holes.

"Firefox 3.6 will be primarily a release with security, stability, speed and capability enhancements, with no visible user interface changes over Firefox 3.5. As such, I think we should consider it as a candidate for a minor update, stretching our definition of what types of updates we can provide using that mechanism," Beltzner said.

Be default, Mozilla automatically distributes minor Firefox updates to be installed after a user prompt. Major updates initially require the user to actively retrieve the new version, though Mozilla gets more active as time passes and older versions reach the end of their support lifespans--January 2010 in the case of Firefox 3.0.

Why change the process? To keep up with changes in the browser world, Beltzner said.

"The pace of technology development in web browsers is speeding up rapidly, and we now face a challenge of ensuring that we can continue to deliver modern web browsing experiences to our users," he said.

And in a position that mirrors the rationale that Google offers for its automatically updating Chrome browser, he added, "Users' expectations of software have changed since the update mechanism was introduced in Firefox 1.5. Many applications that browser users interact with exist in the cloud, with updates pushed frequently and transparently, without consultation. That wasn't the case only a few years ago."

That sounds reasonable, right? Well, it turns out nothing is simple.

One problem is that add-ons won't work with the new version unless they're updated, too, and there are a lot of add-ons in the world. "Add-on compatibility is one of the large reasons why users do not move from one version to another," Beltzner said.

Sure enough, John Barton, an IBM employee who's a member of the group overseeing development of the Firebug add-on widely used in Web site development, raised concerns about moving quickly to 3.6 and the current version 1.4 of the add-on.

"We're a little confused by a Firefox 3.6 that can't decide if it is 3.6 or 3.5.5. If 3.6 is really minor, release it as 3.5.5. Else, well then it's not minor after all," Barton said, though adding, "I support shorter release cycles in Firefox."

Add-on compatibility problems is one reason Mozilla is moving to the new Jetpack extensions system in Firefox 4.0 next year.

One of the big new features in Firefox 3.6, code-named Namoroka, is the arrival of Personas, which lets people customize the browser appearance.

Mozilla said the first beta of Firefox 3.6 is due this weekend or early next week, and Beltzner said there currently are no plans for second beta. The final version is due by the end of the year.