Opened 2 years ago

Closed 2 years ago

#26275 closed task (wontfix)

Do not in-place upgrade to TBB v8 (ESR60)

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Critical Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


TBB updater shouldn't upgrade current TBB 7.x users.
Instead, show a dialogue:

A new TBB is now available!
Please download new TBB from https://tpo

Everyone should start using fresh browser - ESR52 and 60 is completely different.

If you use updater to do in-place upgrade, many people will carry over old settings and some might cause a persistent problem.

Child Tickets

Change History (6)

comment:1 Changed 2 years ago by cypherpunks


  1. Delete any modification from TBB7x (user-installed add-ons and its setings, modified pref.js)
  2. Do upgrade

So everyone's identity should be the same.

comment:2 Changed 2 years ago by sysrqb

This is exactly the type of friction we do not want. Forcing the user reinstall (and re-verify) their installation will prevent many users upgrading. We could offer an option that resets the tor browser preferences to the defaults - but this functionality isn't built into Firefox. Unfortunately, cleansing the entire profile is non-trivial due to the current design. See #16441 (and #24993, #22528, #19135) for some details.

comment:3 Changed 2 years ago by cypherpunks

Despite all the bullshit here, you really shouldn't update esr52 to esr60 without warning.

comment:4 Changed 2 years ago by gk

So, we updated users from esr38 to esr45 and from esr45 to esr52 and Mozilla is regularly updating users from one ESR to the other without issues. Why is suddenly the update from esr52 to esr60 different? And, no, user-installed extensions and modified prefs is not a reason to not to do so as this is something we do not recommend and warn against.

Last edited 2 years ago by gk (previous) (diff)

comment:5 Changed 2 years ago by cypherpunks

gk is right here, users who don't listen to TP guidelines of "DON'T COME ANYWHERE NEAR DEFAULT SETTINGS" will have to swallow their own medicine. So I think instead of doing something crazy as the cypherpunk above suggests that more effort should be put to warn users whenever they come to about:preferences, about:addons etc.

comment:6 Changed 2 years ago by gk

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.