If that ever changes i'll look into making my own Firefox binaries or whatever that have this check removed.
This updates frequently since it is basically Firefox beta (though in practice i never had any issue). Note that this has telemetry enabled by default so you may want to disable it via the options.
Unbranded stable: https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded...
The unbranded stable isn't updated automatically so you'll need to check for new versions yourself (shouldn't be too hard to automate it with a python script or whatever that runs via cronjob or windows task scheduler and notifies you for new versions).
There isn't even a manual review gate for AMO releases after the first one (but it can happen after that fact).
I find Mozilla's policies friendlier than Google's but this is the first I've heard of "extension developer mode" - will have to look into that as my extension is cross browser.
https://extensionworkshop.com/documentation/publish/signing-...
The way I do it now is to package the extension as zip (no webext needed) with a custom manifest, which can be installed by setting xpinstall.signatures.required to false in the about:config page.
On the manifest side, you just need to include this snippet:
"browser_specific_settings": {
"gecko": {
"id": "[email protected]"
}
}about:config xpinstall.signatures.required -> false
zip -0 mywebext.xpi manifest.json *.js *.png *.html
about:addons -> install xpi "browser_specific_settings": {
"gecko": {
"id": "[email protected]"
}
}
I have a few web extensions I wrote in order to customize a few web sites (automate tasks, alter display, etc). After a Firefox update, they were not allowed anymore, because they're not signed. The extensions page cannot load local extensions. Then I discovered the secret debug-extensions page of Firefox where I could load them.
Unfortunately, Firefox removes local extension when it closes. I had the choice between loading each local extension after launching a new Firefox, which mean a dozen of clicks, or installing web-ext in order to sign my extensions, and sign them again after each change (no idea if there were extra actions needed in the process, like manual reload). I opted for a much simple option: with Chromium-based browsers, you can enable the extension-developer mode, and then you're allowed to load local extensions from the normal extensions page. Extensions are kept across restarts.