First Look: First Look: Firefox 2 beta

With the rise of the Internet, and the wide availability of “beta” software (nearly everything Google releases, for instance, is tagged “beta”), we’ve all come to expect betas to be relatively polished and usable products. That typically holds true with The Mozilla Organization and Firefox. Betas of the popular Web browser are highly publicized and widely downloaded without much thought given to the fact that the software may still be a work in progress.

Things are a little bit different with the public beta of Firefox 2.0 released by Mozilla last week. (A final release of Firefox 2 is expected later in 2006.) Before starting my download, I noted this interesting warning on Mozilla’s DevNews page that appeared in bold text no less:

We do not recommend that anyone other than developers and testers download the Firefox 2 Beta 1 milestone release. It is intended for testing purposes only.

Clearly I’m not a developer, but I was interested in seeing what changes and new features are slated for Firefox 2, so I decided I qualified as a tester, since I’m more than willing to crash my machine in the pursuit of knowledge. With that decision made, I downloaded the Universal Binary beta, installed it, and set out to see what’s changed with my second-favorite browser (behind Camino ). While there’s a lot to like about this version and my experience has been pretty stable so far, I would caution anyone who’s contemplating using the Firefox 2 beta that it’s not in any way yet recommended for production machines.

Initial thoughts

To be honest, my first reaction was “huh, did I somehow launch Firefox 1.5 instead of the 2.0 beta?” That’s because the visible structure of Firefox hasn’t changed all that much. It looks like Firefox 1.5, even as you browse through the tabs in the Preferences screen and the menu structure. Sure, there are some visible changes, but you need to look somewhat closely to spot them:

  • Each tab now has its own close button, instead of one global close button at the right edge of the tab bar.
  • When you’re loading a page on a tab, the spinning “site loading” icon no longer overwrites the site’s icon at the left edge of each tab. Instead, the site loading icon is placed just to the right of that spot.
  • The Extensions and Themes entries in the Tools menu have been combined into a new Add-Ons item. The Add-Ons interface itself now has tabs for Extensions and Themes, which is a much more logical structure.
  • There are a few new menu entries and preference settings, such as Anti-Phishing. It’s in features like this one where many of the new 2.0 features are hiding. (More on that in a bit.)
  • If you use extensions and themes, you’ll probably find that the vast majority of those you’ve installed in 1.5 don’t yet work in the 2.0 beta. In my case, only 9 of my 25 extensions, and none of my 10 themes, work in Firefox 2.0. (There are some themes available that work in 2.0, such as Phoenity Modern and NASA Normal.) But this is a standard issue with any major Firefox release—it’s always a bit of a wait until the themes and extensions catch up. Keep in mind this is but the first beta of 2.0 as well, so it’s quite early in the process.

    So if Firefox looks the same as it predecessor, and seems to have few visible changes, why bother with a version jump all the way to 2.0? To answer that question, we must look a little deeper.

    Behind the scenes

    This release of Firefox is being pegged as a major upgrade primarily due to changes that aren’t necessarily visible to the the everyday user. That’s another way of saying that lots of buzzwords have been updated or installed—things like support for JavaScript 1.7, OpenSearch, and SVG’s svg:textPath element. In addition, there’s better security for extensions (as well as better localization support), and session and persistent storage. Taken as a whole, however, these features will eventually make the user’s Web browsing experience better. But from a user’s perspective, these changes are more or less invisible. So what’s in it for the user to upgrade then?

    While the Firefox 2.0 beta looks nearly identical to its 1.5 predecessor, there actually are a fair number of new features of interest to the typical user. Here’s a quick look at some of them, based on my testing with the 2.0 beta 1 release.

    New stuff for the masses

    Anti-Phishing Tool: Firefox 2.0 includes a list of known phishing sites. The Anti-Phishing tab in the Advanced section of Firefox’s Preferences controls this feature, and it’s enabled by default. You can turn it off using the preferences panel, or tell it to use Google (and eventually, other anti-phishing sites) to check the sites you visit. If you attempt to load a page that Firefox has categorized as a phishing site, you get a no-way-you-can-miss-it warning:


    Because phishing sites change rapidly, Firefox’s list of sites is updated “regularly,” though at this early beta stage, there’s only a limited list of sites. Future beta releases will include a longer list, as well as an easy way to report both additional phishing sites as well as false positives (valid sites that have been flagged as phishing sites). For now, then, the anti-phishing feature is in the “soon to come” category. But with the increasing sophistication of phishing emails, the final version of this tool will be most welcome.

    Spell Check: Firefox will now spell check words in text fields, as you type. When you type a words the browser can’t locate in its dictionary, it gets flagged with a dotted underline. Control-click on the underlined word, and the contextual menu will offer replacement words, as well as the ability to add the word to the dictionary. What’s lacking, at least as of beta 1, is the ability to simply ignore a word, instead of being forced to add it to the dictionary if you don’t want to change its spelling. While I’d much prefer Firefox to simply use the built-in OS X spell checker, this solution works (though it does mean you’ll be maintaining two dictionaries, one for OS X apps and one for Firefox).

    Search enhancements: There are two main improvements in search. The first is that the search box is now customizable. Click the drop-down arrow next to the magnifying glass and select Manage Search Engines. When you do so, a small drop-down box appears, letting you reorder the list of existing engines, as well as add or remove other search engines. Unfortunately, you can’t define your own search engine, at least in this beta release. Instead, you’ll have to pick from a list of Mozilla-provided engines, which you reach via a URL link in the Manage Search Engines box. Hopefully future releases will allow easy addition of your own search sites.

    The other improvement in search is the new “search suggestions” feature. As soon as you start typing your search term, Firefox opens a list of possible search terms, based on what you’ve typed so far (as seen in the image on the right). At the top of the list are any searches from your search history; below that are matches based on what you’re typing. In testing this feature, I found that my search term often wound up near the top of the list after only a few characters of typing (even when not retyping something that was already in history). This little feature could prove to be quite the typing timesaver.

    Session Restore: If Firefox crashes, it will now reopen tabs, resume downloads, and bring back any text you had typed in forms at the time of the crash. This worked well when I tested it (by force-quitting Firefox). However, you’re also supposed to be able to reopen accidentally-closed tabs or windows, and I couldn’t figure out how to do that (without resorting to History, which has always worked in most any browser). For more robust session saving, however, I still rely on the SessionSaver add-on, which has a few more features. (And it’s already updated for the 2.0 beta).

    Bookmark microsummaries: Typically, bookmarks are stored with either the title of the page they refer to, or a name the user creates for that bookmark. Firefox 2.0 adds a third naming method, microsummaries. A microsummary is a dynamic title for your bookmark, set by the site you’ve bookmarked. So instead of seeing Merriam Webster Dictionary Word of the Day for your bookmark title, you can actually see the word of the day—and it will change each day.

    For this feature to work automatically, you must first install a microsummary generator for a site (and the site must, obviously, have a generator available). Then, you bookmark it and click a pop-up field in the bookmark entry screen to change the name to the micosummary.

    After playing with this for 30 minutes or so, I still don’t get it—why would I want the name of my bookmarks to change regularly? Besides, at least as of this beta, the microsummary name doesn’t show in the Bookmarks menu; only on the Bookmarks screen, or in the sidebar. Thanks, but I think I’ll stick with the traditional method of naming bookmarks. Perhaps in later betas, this feature will become more impressive. For now, it’s not something I plan on using.

    Improved ‘feed’ handling: Feeds, known by various other names including RSS and content syndication, are a great way to keep up with active Web sites. You can use a feed reader such as NetNewsWire to see an often-updated list of stories on a given site, making it easy to keep up without having to reload the homepage in your browser. (Safari can also manage feeds.)

    In Firefox 2, when you visit a site with a feed and then click the feed icon in the URL bar, you’ll get a nicely-formatted presentation of the feed’s contents, as well as options for how to handle the feed (use a live bookmark in Firefox, use an external reader, and so on). This is a nice improvement over the current browser, which merely creates a live bookmark when you click the feed icon in the URL bar.

    About that warning

    As you’ll recall, the Mozilla group doesn’t recommend Firefox 2 beta for most users. Despite that warning, however, I didn’t experience a single crash during testing, and most features were functional. There are definitely some rough spots—I couldn’t get Command-W to close the last window, for instance, and the help files have yet to be updated. But such things are to be expected in an early beta; I was actually surprised that I didn’t have more troubles with the program. For heavy users of Firefox’s numerous extensions and themes, the lack of compatibility will probably be a show stopper. But as a portent of things to come in the final release of Firefox 2, this first beta is a good sign.

    The last word

    Would I recommend anyone use Firefox 2 beta 1 as their primary browser? That would probably depend on how the individual uses their browser. If it’s a casual usage, just scanning some news and tech sites a few times a day, then I’d probably say “go ahead,” with the understanding that you’d be using an incomplete product. But if you’re in a situation where a browser is a key component of your workflow, then I’d recommend sticking with Firefox 1.5 (or your current preferred browser), as the new features probably aren’t worth the possible risks of lost productivity due to crashes. (Imagine losing your bookmarks file, for instance, if something went terribly wrong.)

    Overall, though, I was impressed with the stability, feature set, and general performance of this first public beta. It will be interesting to watch as Firefox 2.0 evolves from this first beta to a released version sometime later this year.

    [ Rob Griffiths writes the Mac OS X Hints weblog and runs macosxhints.com. He took a first look at Firefox 1.5 when it was released late last year. ]

    Subscribe to the Apple @ Work Newsletter

    Comments