Another new version of Firefox was announced on April 29.

Version 29 is touted by Mozilla as ‘elegant’ and ‘the most customizable’ Firefox ever, but there’s been a lot of noise on the web from people who are unhappy with the user interface changes.

It’s not really clear why many major browser developers are trying to make their browser look exactly like Google’s Chrome, but that does seem to be what’s happening. A few months ago, Opera chucked their browser engine in favour of WebKit, with the result being that Opera is now almost indistinguishable from Chrome. Mozilla hasn’t gone that far: their browser engine hasn’t changed, but in terms of appearance, Firefox now looks a lot more like Chrome. Perhaps they think that if Firefox looks like Chrome, users won’t realize they’re not actually using Chrome.

Has anyone done any actual usability studies on these UI elements that are now so popular among developers, like rounded corners on everything? Do rounded corners make people more productive? I doubt it. Another example is Firefox 29’s tab bar, which (besides having those awesome rounded corners we should apparently care so much about) now makes unselected tabs fade out so that they are hardly visible. How is this a good thing? Mozilla seems to think that being able to read what’s on those unselected tabs is a major distraction. Nope.

As for Firefox 29 being more customizable, I beg to differ. I was previously able to open and close the bookmark toolbar with a single click of a toolbar icon. That icon is nowhere to be seen in Firefox 29. Instead, I now have to click the ‘Show your bookmarks’ icon, then click ‘View bookmarks sidebar’. This is progress?

The release notes page for Firefox 29 lists several new features and changes, none of which are particularly useful or interesting.

The best thing about Firefox 29, in my opinion, is that web site favicons – those little icons that appear next to the page title in the tab bar and desktop shortcuts – now seem to work reliably. Previous Firefox versions had a lot of trouble with some favicons.

Several security issues were fixed in version 29, so even if you think you’ll hate the new UI, you should probably upgrade anyway.

On a related note, despite my having diligently reported my problems with the Firefox release notes pages (bug #973335) and version announcement pages (bug #973330), Mozilla has done nothing to improve them, as you can see from the pages for Firefox 29.

Ars Technica has their own review of the changes in Firefox 29.

There was yet another stealth release of Firefox yesterday. Version 28 was not announced on any of the myriad Mozilla blogs. I only discovered it because of release announcements on CERT and SANS blogs.

According to SANS, at least some of the security fixes in Firefox 28 are the result of successful hacks at the recent Pwn2Own contest. There’s a full list of the security fixes in this version at the top of the ‘Known Vulnerabilities‘ (aka ‘Security Advisories for Firefox’) page for Firefox.

The official release notes page for version 28 shows no improvement over previous release notes pages. But it does list the changes in the latest version, none of which are worthy of note.

Aside: I recently submitted two bugs to the Mozilla bug tracking system for Firefox. Bug #973330 is about the lack of proper announcements for new Firefox versions. Bug #973335 covers the many issues with the release notes pages for Firefox. So far the responses from Mozilla workers have not been encouraging.

Another new version of Firefox slid quietly off the production line yesterday. Version 27 improves interactivity with certain social web sites, and fixes a few bugs, including a dozen security vulnerabilities.

As usual, the only announcement of the new version was in the form of a post on the Mozilla Blog, which fails to mention that the post is actually about a new version of Firefox. The official release notes for the new version are as usual a total mess, barely even mentioning the new version identifier.

Tuesday saw another stealth release of Firefox: version 26. As usual, the new version was not announced by Mozilla; I learned about it from a post on the CERT Current Activity blog. The official release notes for version 26 describe some of the changes in this version: nothing worthy of note. Version 26 does include fixes for some security issues, so you should upgrade as soon as possible.

Update 2013Dec16: One notable change in Firefox 26 is that Java is now blocked on all sites by default. This behaviour can be changed, but we recommend using the default setting.

Another stealth release of Firefox happened on November 15. Version 25.0.1 apparently fixes some security vulnerabilities and other bugs. With the total lack of any kind of announcement for this release, and the way the release notes include changes in previous releases, it’s difficult to be certain what’s new in this version. For instance, the version 25.0.1 release notes point to the ‘Known vulnerabilities‘ page, but there’s nothing listed there that’s specific to version 25.0.1. The release notes for 25.0.1 also point to Bugzilla (‘complete list of changes‘), but the list of fixed bugs shows everything for version 25, and nothing specific to version 25.0.1. What a mess.

Update 2013Nov23: EWeek has more information about the security vulnerabilities fixed in Firefox 25.0.1 (even if Mozilla doesn’t).

Mozilla released Firefox 25 on October 29, with the usual lack of any kind of announcement. I was alerted to the new version via posts on the SANS ISC Diary and the CERT alerts list.

The only thing even close to an announcement of the new version from Mozilla is a blog post from the 29th that describes one of the new features in Firefox 25. The blog post never even mentions the new version.

The version 25 release notes list the changes in this version, which consist of several security vulnerability fixes, a few other bug fixes, Web Audio support, and some CSS and HTML standards tweaks.

The Known Vulnerabilities page shows the security-related fixes in version 25.