Add-ons/Firefox57

From MozillaWiki
Jump to: navigation, search

This document is to clarify on the myriad of choices for loading extensions in Firefox and what will happen in Firefox 57. There is a bug for this. This document expands it.

The main goal is prevent the running of legacy add-ons in Firefox Desktop release. None of the above applies to Android until we feel confident in the APIs available and apply similar changes to Android.

Reference: list of add-on types

Compat. Table

This is what things will look like when Firefox 57 hits release.

Type Status Nightly, Aurora Beta, Release
WebExtension Signed by AMO YES YES
Signed by Mozilla internally YES YES
Unsigned YES with pref NO
Unsigned loaded temporarily YES YES
Legacy Extension (bootstrapped, overlay, XUL etc) Signed by AMO YES with pref NO
Signed by Mozilla internally YES YES
Unsigned YES with pref NO
Unsigned loaded temporarily YES NO
WebExtension Experiment Signed by AMO YES NO
Signed by Mozilla internally YES YES
Unsigned YES with pref NO
Unsigned loaded temporarily YES NO
New style static theme Signed by AMO YES YES
Signed by Mozilla internally YES YES
Unsigned YES YES
Unsigned loaded temporarily YES YES
Telemetry Experiments Signed by AMO YES YES
Signed by Mozilla internally YES YES
Unsigned YES with pref YES
Unsigned loaded temporarily YES YES
Legacy lightweight theme Signed by AMO YES YES
Complete Themes Any combination YES with pref NO
Multiple item package Any combination NO NO
Language Pack Any combination YES YES
Dictionaries Any combination YES YES

Notes

  • Nightly and Aurora will need to flip prefs
    • For unsigned the appropriate signing pref must be flipped.
    • For legacy add-ons the appropriate pref must be flipped.
    • Both of these will default to false.
  • AMO will stop signing legacy add-ons for version of Firefox greater than 57. Old signed add-ons will remain on servers and people's hard drives, so although AMO will stop signing them, we still need an explicit block in Firefox to prevent them loading.
  • "Signed by Mozilla internally" refers to add-ons signed internally and might include Test Pilot, Shield and other add-ons.
  • If we support loading unsigned temporarily, it’s assumed we load signed temporarily too.