1385251 - Legacy Extensions are not automatically disabled after switching to a build with extensions.legacy.enabled set to false by default

Status: RESOLVED INVALID

(Toolkit :: Add-ons Manager, defect)

Description

[Vasilica Tamas, QA [:vtamas]]

Attachment: 2017-07-28_1143.png

[Affected versions]:
Firefox 56.0a1 (2017-07-27/28)

[Affected platforms]:
Windows 10 64-bit
Ubuntu 16.04 32-bit

[Steps to reproduce]:
1.Launch Firefox with a clean profile.
2.Install several legacy add-ons. 
3.Close the browser.
4.Create a user.js file in the profile folder and save the following line: user_pref("extensions.legacy.enabled", false);
5.Open Firefox and navigate to about:addons -> Legacy Extensions tab.


[Expected Results]:
All legacy add-ons are automatically disabled and moved to “Legacy Extensions” tab.

[Actual Results]:
- All legacy add-ons are moved to “Legacy Extensions” tab but they are still enabled. They are disabled only after a while. The period varies between a few minutes and a few hours.
- See attached screenshot.

Comment 1

[Andrew Swan [:aswan]]

In the STR provided, you're not actually switching builds, you're just flipping a preference.  If when the browser starts up it is running the same version that was previously run in that profile, it just loads all the extensions that were previously loaded.  If the application version has changed, then it looks at each installed addon and checks whether it should be disabled.
So, if the goal is to test what happens during the 56->57 upgrade cycle, we'll need new builds that use a new version.  I can create those for you if you like, please open a separate bug for that and specify which platforms you would like.