Closed Bug 1384610 Opened 7 years ago Closed 7 years ago

Complete theme remains enabled and installed after setting extensions.legacy.enabled to false

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
firefox54 --- unaffected
firefox55 --- disabled
firefox56 --- affected

People

(Reporter: vtamas, Unassigned)

References

Details

Attachments

(1 file)

Attached image Animation1.gif
[Note]: 
This is a follow-up for Bug 1373449

[Affected versions]:
Firefox 56.0a1 (2017-07-26)

[Affected platforms]:
Windows 10 64-bit
Mac OS X 10.12.3

[Steps to reproduce]:
1.Launch Firefox with a clean profile.
2.Install the following complete theme: https://addons.mozilla.org/en-US/firefox/addon/lavafox-v1/?src=cb-dl-users
3.Restart the browser.
4.Navigate to about:config and toggle "extensions.legacy.enabled” pref to false.
5.Restart the browser.
6.Go to about:addons and check the complete theme status.


[Expected Results]:
Complete theme is automatically uninstalled and displayed in Legacy Extensions tab.


[Actual Results]:
- At step 4 in about:addons -> Extensions appears the following message for the installed complete theme “LavaFox V2 will be disabled after you restart Nightly”
- The complete theme remains installed after restarting the browser. It is displayed as disabled in “Recent Updates” tab together with the “LavaFox V2 has been disabled since it is not multiprocess compatible”
- See attached screencast.
Summary: Complete theme remains installed after setting extensions.legacy.enabled to false → Complete theme remains enabled and installed after setting extensions.legacy.enabled to false
This is the same issue as described in https://bugzilla.mozilla.org/show_bug.cgi?id=1385251#c1
In short, the browser does not re-evaluate compatibility restart with a pref flip.  So I don't believe this will be a problem during the upgrade-to-57 cycle (though that could be verified with the builds in bug 1385964).  And then after 57, support for complete themes will go away and this will no longer be an issue.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: