Although after the release of Firefox 1.0 I stuck with the official build for quite a while, for the past few weeks I’ve been back onto nightly trunk builds. These are the development builds that will ultimately form Firefox 1.1 when it is released this summer.
In a week’s time, it will have been 6 months since the release of Firefox 1.0, so what has happened to the trunk since then? I’m going to use this entry to give an overview of the work that has been done over the past 6 months and the work that is still pending but will also make it into 1.1.
- Support for Scalable Vector Graphics (SVG), an open format for drawing vector graphics in a web browser. Opera 8 also supports this.
- New, easier-to-use Options dialog that also looks better on Mac OS X. Includes major improvements to how downloads are handled.
- ‘Sanitize Firefox’ – an easier way to clear history, cookies, saved passwords etc., including the ability to sanitize when the browser is closed.
- Speed improvements, especially when a Firefox profile is stored on a network drive since the interface and web page caches can now be stored separate from the profile (see this blog post).
- Improved handling of extensions (see this blog post). Bad extensions may also be blacklisted (see Wiki entry).
- Improved update system, which should mean that security updates can be delivered in patch form. An upgrade from 1.1 to 1.1.1 should no longer require downloading the full version all over again.
- Support for installation using Windows Installer on Windows, which should aid roll-out in enterprises.
- Better rendering of web pages, including the infamous Slashdot bug.
This probably isn’t everything so if I’ve missed something important let me know in the comments. In any case, even with just the above new features, Firefox 1.1 is going to rock.