FireFox 1.5

Everybody seems to be writing about the new firefox and as a loyal user, I shouldn’t stay behind. I’ve been using the alpha and beta versions and they have proven to be mostly trouble free (as much as you could expect from alphas and betas).

The alphas were a little unstable and I encountered a couple of crashes (over a period of several weeks). That hasn’t happened to me with the beta which I’ve been using since it was released. The largest problem has been the intially slow pace with which extensions are tested and ported. By now most of the more relevant (and actively maintained) ones have been ported. There are still a few extensions missing. Presumably the developers are waiting for the final release or simply not interested in immediately fixing their extensions.

Now the new features. At a first glance, not much has changed. Most changes are under the hood. The most visible change is no doubt the rearranging of the preferences dialog. IMHO it doesn’t make much difference but I agree it is slightly nicer this way. Also the rss button has relocated from the status bar to the locationdropdown. IMHO this is slightly awkward or at least unconventional. And finally FireFox now has error pages for timeouts and other server errors, just like IE has had for years. Other than that, I can’t think of any relevant, eye catching changes.

Then there are the changes under the hood. SVG and canvas are two new cool technologies. However, since internet explorer does not support these, I doubt they will be used very much. Firefox only sites are a bad idea IMHO. Sadly, this also applies to the CSS improvements (e.g. css 3 columns) and javascript improvements. Nice, but it’s not likely these technology improvements will see much adoption (except maybe in browser extensions where browser compatibility is not an issue).

The most visible change to end users will be the performance increase. When 1.0 was released last year, it was released off a branch which had been frozen quite some time by then. Meanwhile development on trunk (a.k.a. mozilla 1.8) continued and about 1.5 year of development has accumulated there, most of which will end up in FireFox 1.5. FireFox 1.5 has a new clever mechanism for back and forward which prevents it from rerendering a page and caches the results. Consequently, going back and forth between pages is now fast. Also normal rendering of pages has seen some improvements. It is hard to quantify this but it certainly feels faster.

Something that is often overlooked in reviews such as this is extensions. As I said there are some porting issues but these will go away when the final release approaches. What is worth noting is that some extensions have really evolved from nice toys to real valuable browser additions. IMHO the added value these extensions provide is often overlooked. You can’t really imagine doing web development without such powerful tools as the javascript debugger, the webdevelopment toolbar, live http headers and many more developer oriented tools. As a mere user, adblock, sage, forecastfox and context highlight make life so much easier and fun. And there are loads more of mature, well tested, valuable extensions.

So to summarize, some minor feature and gui development, lots of under the hood changes which you will notice in the form of snappier performance. Other than that it is still FireFox, a damn good browser, a solid upgrade from any browser you currently use.

4 Replies to “FireFox 1.5”

  1. Ruud Steltenpool emailed me and said:

    reacting on:
    “Then there are the changes under the hood. SVG and canvas are two new
    cool technologies. However, since internet explorer does not support
    these, I doubt they will be used very much. Firefox only sites are a bad
    idea IMHO.”

    It’s not unlikely you already know, but..

    – IE can do SVG with a plug-in, usually ASV (Adobe SVG Viewer)
    – Firefox is not the only browser implementing SVG. There are more
    browsers implementing this W3C standard. Both on the desktop and on mobile
    – SVG is far from only used in browsers

  2. As I replied to Ruud by email, he is of course right except for the fact that Firefox has support for svg dom manipulation through javascript and css. Also svg documents can be embedded in xhtml documents by including the namespace. These two tricks are new and unlikely to be supported in internet explorer and therefore I predict that widespread adoption of SVG on websites will not result from the (now) excellent support in Firefox.

Leave a Reply