Limit the types of add-ons that can be loaded into Firefox. The aim is to turn this on in Firefox 57, but we'd like to land this sooner so we can perform adequate testing. For that reason we'd probably do something similar to signing where its a preference that users can turn on or off and then set it to be ignored at the right point. The only things to load with this flag are: - WebExtensions - Dictionaries - Language packs - New style themes - Lightweight themes - and bootstrapped add-ons if they are signed by a certain certificate
Also of note, this only applies to Firefox Desktop and NOT any other application.
Note that we still have to allow the classic default theme to be selectable in the UI somehow.
A document outlining all the possible configurations is here: https://docs.google.com/document/d/17lu17QShEo-P9cBxiobPQeUb-4HF0cfyN0rFXyOBgJo/edit?usp=sharing
Moved the google doc into a wiki page: https://wiki.mozilla.org/Add-ons/Firefox57
>Legacy lightweight theme - Unsigned YES with pref YES I'm guessing that last "YES" should be a "NO"?
So this means that all current complete themes will become obsolete? Or is/will be there a way to convert them to the new system?
(In reply to Alfred Kayser from comment #6) > So this means that all current complete themes will become obsolete? > Or is/will be there a way to convert them to the new system? Please see the FAQ. The short answer is that complete themes won't be supported, but there is a new theming API. The dev-addons mailing list is probably the right place to discuss this further. : https://wiki.mozilla.org/Add-ons/2017#Q.2BA
Is there a bug to track flipping extensions.legacy.enabled on Nightly? I couldn't find it in dependencies.
(In reply to Masatoshi Kimura [:emk] from comment #8) > Is there a bug to track flipping extensions.legacy.enabled on Nightly? I > couldn't find it in dependencies. Filed bug 1388355 anyway. Feel free to dupe it if it already exists.
All 21 (!!) of the dependencies are resolved, closing.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.