This has been a MAJOR PROBLEM FOR ME for me since at least the time Quantum was released.
My goal during an update is to be able to continue using the release that is to … (tuilleadh eolais)
This has been a MAJOR PROBLEM FOR ME for me since at least the time Quantum was released.
My goal during an update is to be able to continue using the release that is to be replaced until I am satisfied that the new release with its new profile includes as many of the preferences, add-ons, passwords, and other settings that can be carried forward from the previous one as possible (e.g., all that do not cause major conflicts or other serious problems not easily resolved).
The majority of the add-ons I use are related to maintaining the privacy, anonymity, security, and integrity of the browser as well as the data which it handles or manages. Quite a few are redundant so I usually have several installed but disabled at any given time.
From my perspective It makes little sense to enable Firefox to send anything to Mozilla (e.g., allow Firefox to phone home) before I am reasonably sure the new installation of Firefox is running well, with the same or a similar set of security and privacy add-ons in place, especially when I was not made very aware that enabling this would make restoring the add-ons I cherish easier in some way.
Storage is dirt cheap these days. Even on this laptop, I can add another 2TB of fast SSD storage via an external port, then move at least a 1TB of stuff off the 1TB internal SSDs -- in other words, I like the idea of having the option of making a complete backup of the entire existing Firefox Beta release I have been using with all of its pointers to my data on this system, other systems, in the cloud, etc. before letting the installer create the new installation for the upgraded Beta Release.
I gather a system reboot (or at least a browser restart would be in order at this point. After that, it would be wonderful if I was presented the option of migrating all of my old preferences, other settings, and passwords to new profile of the new installation. I doubt many of the add-ons I use are so obscure that they would not get tested by at least a few people doing QA for the upgrade so if any might pose problems, I could be told they could not be migrated with the rest that can be carried forward in a routine manner. (Specific instructions as to how to handle the exceptions would be nice. Some hints about why the particular add-on does not play well with the upgrade would give users a place to start investigating.)
What bugs me the most is that I am dead in the water until the add-ons that I use to block a shit-ton of tracking, fingerprinting, and other kinds of cookies, as well as those used by outright malware disservices found on some sites are in place to make the Web a much safer place for me and the things I use it for.
I completely understand why the upgrades to the first releases of Firefox Quantum required most users to re-install most addons and set most of their preferences, but after a major release upgrade or three to Quantum, things should be back to a lot more automated routine that preserves the functionality the user had in the previous release as much as is realistically feasible when the new release is installed in its own separate place with its own profiles, thus giving the user the fall back option of continuing to use the old release until the new one is tweaked enough to be workable for the user.
Remember: if you do not want to shed users because they get tired of having to restore things from scratch and perhaps losing a lot of important data or functionality along the way, you have to give them as clear and reliable means as possible of getting from where they where (presumably) somewhat satisfied with the old release to as good or better level of satisfaction with the new release, without making them jump through a lot of difficult hoops or perform what seem to be several arcane rituals.
In short, the default process should be to carry forward as many add-ons and user preferences as possible during an upgrade (given the user the option to start from scratch if he likes clean installs or happens to be enough of a masochistic geek to want to go through setting up two dozen add-ons and many specific settings). On occasion, I will put of with the painful process of cleaning the junk out of an old browser or system configuration, but usually I try to do that as part of routine housekeeping and like it when what should be a simple system or browser upgrade does not end up seeming like going through a full tax audit.
Regards,
TMG