Mozilla, Firefox and the Version Number Chaos

Firefox’s rapid release schedule has not been the success Mozilla hoped. Most web developers agree it’s good for HTML5 feature evolution but it’s not without problems:

• Add-on compatibility. Most of us use extensions which cannot keep up with Firefox’s development progress.
• Increased effort. The majority of IT departments must test mission-critical applications before a browser update can be deployed throughout the enterprise.
• Confusion. Few people understand the rationale behind major version increments. Why shouldn’t Firefox 6 be version 4.2?

Mozilla is replicating Google’s release model but Chrome does not necessarily exhibit the same problems. It’s add-ons system is far simpler; more akin to bookmarklets than integrated code. The browser also has fewer legacy hurdles and has silently updated since the early days. Those using Chrome either understand this concept or don’t care. One solution Mozilla considered was the removal of version numbers from Firefox’s “Help > About” dialog. Mozilla’s logic:

1. Few users understand version numbers.
2. Removal would simplify the UI.
3. Users would be informed when the last check occurred, whether they were using the latest version, and how they could update (if Firefox had not automagically done so).
4. If you really needed the version number, it could be found in about:support.

Uproar ensued on Bugzilla and the associated newsgroup discussion. The majority of respondents detested the idea (although a large volume of ranting and spam appeared when Mozilla’s intentions went public) . The organization put forward some reasonable arguments but ultimately backed down. Mozilla’s Robert Kaiser:

Can we close this bug report? Version numbers in software are like coordinate systems in physics: irrelevant and necessary at the same time — it’s completely irrelevant how you do them, but they provide necessary reference points. Not more, not less. Where ever we go with this, I don’t think it will have either a large impact on version number messaging or on making Firefox useless, so I think the rage on both sides is overrated.

The reply from VanillaMozilla:

Done … I’m having a hard time finding anyone at all who thinks this is a good idea.

The argument become overheated but Mozilla’s proposition had a number of flaws:

1. It went against established UI conventions that span OSes and 20+ years of IT development. There may be better ways, but removing version numbers is not likely to be the best solution.
2. The proposal was too simplistic and did nothing to tackle Firefox’s rapid update issues. Version numbering was never the cause or the cure.
3. Users may not understand version numbers, but removing them was a non-issue. Firefox wouldn’t suddenly become easier to use.
4. There are multiple versions of Firefox in the wild. Some would have version numbers, some wouldn’t. None of the older editions would state they were out of date.
5. Version numbers are important to developers and IT support staff. What’s the first question you ask when someone reports a problem in a specific browser?

Version numbers have been rendered meaningless in Chrome and Firefox. Few people know or care what version of Chrome they’re running. Perhaps, one day, the same will be true for Firefox — but we’re not there yet. Firefox is an older browser with far more baggage and a large, passionate user community. Mozilla ultimately listened to their demands, but the the proposal and subsequent onslaught did nothing for the browser.

Frequently Asked Questions (FAQs) about Mozilla Firefox Version Number