Re: Removing Firefox Version Number

On Aug 25, 5:01 am, SarahWriter <[email protected]> wrote:
> The version number is unimportant only if
>  - new versions do not contain new or changed features
>  - new features never cause difficulties in other pieces of software
>
> But in the world of customer service, where Firefox interacts with
> other software programs, it's extremely important to know what version
> and point version the customer is running.  Some work; some don't.  If
> a software change in my browser keeps features of my Web-based program
> from running, I have to know which version I'm running (and have to be
> able to back out of it).

Key point. Just today Firefox has updated itself from 5.0 to 6, and
promptly disabled my Java Console add-on, stating that it is not
compatible with this version of Firefox. Searching the interwebs, this
appears to have lead to a lot of consternation from users who believe
that Java has been disabled (rather than just the useless Java
console) - the advice from Mozilla is that because the Java console
does not serve any useful purpose to most users, then it doesn't
matter that it is disabled in the latest version of Firefox. But if
updating the version can lead to breaking the product of a major
company like Oracle, then how can corporate (or home) users be
confident in upgrading when it could well break other extensions that
they rely upon?

I've already turned off auto-updates in Firefox from now on - will
wait to see the effects of each upgrade before I allow firefox to
update itself. The plan to remove the version number is as you say
premature. First make it so that firefox updates within the rapid
release schedule do not break extensions and add-ons. Then remove the
version number once it becomes irrelevant.