Closed Bug 1373422 Opened 8 years ago Closed 8 years ago

Non-restartless legacy extensions aren't disabled without a restart

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: krupa--use, Unassigned)

References

Details

56.0a1 (2017-06-15) (64-bit) steps to reproduce: 1. In about:config, toggle the value of extensions.legacy.enabled to true 2. On your nightly install a restartless legacy extension like NoScript. Make sure NoScript is working. 3. In about:config, toggle the value of extensions.legacy.enabled to false 4. Load about:addons 5. Notice that there is warning that noScript will be disabled after restart expected behavior: If extensions.legacy.enabled to false, then all legacy extensions are disabled. observed behavior: Only restartless legacy extensions are disabled. If the user doesn't restart the browser, a legacy extension like NoScript will keep running even though the pref is toggled to not support them. Things to check: * Need to make sure that when the user upgrades to 57, the browser upgrade takes care of the add-on disable as well. For andy and kev: Is this behavior something we are okay with?
Flags: needinfo?(kev)
Flags: needinfo?(amckay)
Summary: Restartless legacy extensions aren't disabled without a restart → Non-restartless legacy extensions aren't disabled without a restart
When a browser upgrades to Firefox 57 there will be a restart and the add-on won't be loaded. It's an unfortunate legacy of non-restartless add-ons. I'm fine with this behaviour.
Flags: needinfo?(amckay)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Concur. (In reply to Andy McKay [:andym] from comment #1) > When a browser upgrades to Firefox 57 there will be a restart and the add-on > won't be loaded. It's an unfortunate legacy of non-restartless add-ons. > > I'm fine with this behaviour.
Flags: needinfo?(kev)
You need to log in before you can comment on or make changes to this bug.