Why don't we just turn off MOZ_BLOCK_PROFILE_DOWNGRADE?
mbanner at mozilla.com
Fri Jul 5 08:09:13 UTC 2019
On 04/07/2019 08:30, Nomis101 🐝 wrote:
> I see this exacly the same. I never found any problem while downgrading Thunderbird. The first real issue after downgrading I ever
> had was MOZ_BLOCK_PROFILE_DOWNGRADE. For a test I downgraded from TB 68 to 60 and even to 45.8, but could't see anything broken.
I would just like to point out that whilst "you" personally (not just
talking about you, but those responding here in this manner) haven't
seen any issues, that doesn't mean to say there aren't.
For example, this is one I hit during Hello development:
It is a little while ago, but I think that would have affected any
user's indexeddb database(s). Though it probably wasn't so widely in use
at the time.
Note also this section from the original announcement
for the change:
Firefox stores all of its settings in the user’s profile and unless certain
command line arguments are used Firefox always launches with the same
profile. Periodically as Firefox upgrades it makes changes to the settings
that can render the profile unusable by earlier versions of Firefox. This
can cause anything from certain features of Firefox being broken after a
downgrade to Firefox crashing on startup.
I don't have any citations for these, but I somehow doubt we'd just be
making this up.
> For beta testing and regression finding you often have to downgrade, which is now very frustrating. And it also happens very often
> that a normal user is downgrading. I'm in a Mac user forum and a lot of support questions there are regarding downgrading to an older version
> of any given software (because of dislike the new UI, missing features in the new version or whataver reason).
Developers can use --allow-downgrade to skip the protection.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tb-planning