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 hits release and for each release past that (as far as we can see, things may change). There is a bug for this. This document expands it.

The main goal is prevent the running of legacy add-ons in Firefox Desktop and Android release. Update: All of the following apply to Android and Desktop.

Reference: list of add-on types

Compat. Table

This is what things will look like when Firefox 57 hits release and for each release past that (as far as we can see, things may change).

Type Status Nightly 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 NO
Unsigned loaded temporarily YES YES
Legacy lightweight theme Signed by AMO YES YES
Complete Themes Any combination NO NO
Multiple item package Any combination NO NO
Language Pack Any combination YES YES
Dictionaries Any combination YES YES

Nightly leading up to Firefox 57

To assist with performance analysis leading up Firefox 57, in Nightly only we are turning off add-ons that require shims. For more information please see shims on nightly. The pref will default to false.

Type Status Nightly Beta, Release
WebExtension YES YES
Legacy Extension (bootstrapped, overlay, XUL etc) MPC=true YES YES
MPC=false YES with pref YES
MPC not stated YES with pref YES

An extension must pass both tests to run. Example:

  • A XUL overlay extension that is signed by Mozilla and is MPC=false, *will not run* on nightly unless the user changes the pref.
  • A XUL overlay extension this is signed by AMO and is MPC=true, *will run* on nightly.
  • A WebExtension that is unsigned *will run* on nightly but not on release.

Prefs

To enable things on Nightly some prefs must be flipped:

  • For unsigned the appropriate signing pref xpinstall.signatures.required must be flipped.
  • For legacy add-ons the extensions.legacy.enabled pref must be flipped.
  • For non-MPC add-ons extensions.allow-non-mpc-extensions pref must be flipped.

Notes

  • 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.

Updates

  • Removed Aurora from this chart.
  • Added in the Nightly MPC=True changes.