diff options
author | girst <girst@users.noreply.github.com> | 2022-04-29 15:31:44 +0200 |
---|---|---|
committer | girst <girst@users.noreply.github.com> | 2022-04-29 16:15:47 +0200 |
commit | 0548b59e51d966622e8733c62690078b61713d48 (patch) | |
tree | 865b71c197e4387e58a0fabd1e471182e01be82c /legacy/BootstrapLoader.jsm | |
parent | e6c78f51e895cb0d08f427721d01d1909b4c92a8 (diff) | |
download | legacywolf-0548b59e51d966622e8733c62690078b61713d48.tar.gz legacywolf-0548b59e51d966622e8733c62690078b61713d48.zip |
Do not override AddonSettings.REQUIRE_SIGNING
This is not necessary, as it is only checked in
XPIDatabase.jsm::mustSign(), which we can override instead, and in
aboutaddonsCommon.js::isDisabledUnsigned(), which we cannot affect
anyways and only uses it to show a red warning bar for legacy addons.
This also removes the old AddonSettings.ALLOW_LEGACY_EXTENSIONS
override, which was only used in Extension.jsm::experimentsAllowed()
and XPIDatabase.jsm::isDisabledLegacy().
This is in preparation for the ESM-ification endeavours going on at
Mozilla, which will make importing a module's global object (as we did
with `let Xdb = Cu.import(...)`) impossible, but was needed to get a
reference to AddonSettings (instead of a copy). Step two will be
replacing Cu.import() with ChromeUtils.import(), which has stricter
semantics about exported objects (doesn't hurt us; see Bug 1766114).
Diffstat (limited to 'legacy/BootstrapLoader.jsm')
0 files changed, 0 insertions, 0 deletions