4 ms·

Firefox is odd in this regard, though. Chrome tried to make it so you could only add extensions while signed in to Google, but have since abandoned that policy

Firefox is odd in this regard, though. Chrome tried to make it so you could only add extensions while signed in to Google, but have since abandoned that policy and currently permits side loading, while Firefox doesn't allow any extensions that haven't been signed by their certificate which means that if they forget to renew that certificate you can't use any extensions...which actually happened. It's bizarre to me that Chrome offers more user agency in this regard than Firefox.

commoner 5y ago
On desktop, Firefox Developer Edition, Nightly, and ESR still allow unsigned extensions after setting xpinstall.signatures.required to false in about:config.[1] Firefox for Android doesn't allow sideloading,[2] and only has an advantage because Chrome for Android doesn't support extensions at all in its official relases. [1] https://wiki.mozilla.org/Add-ons/Extension_Signing#FAQ https://wiki.mozilla.org/Add-ons/Extension_Signing#FAQ [2] https://github.com/mozilla-mobile/fenix/issues/11308 https://github.com/mozilla-mobile/fenix/issues/11308 (closed without adequate resolution in https://github.com/mozilla-mobile/fenix/issues/14034 https://github.com/mozilla-mobile/fenix/issues/14034)
- GravitasFailure 5y ago
  >On desktop, Firefox Developer Edition, Nightly, and ESR still allow unsigned extensions after setting xpinstall.signatures.required to false in about:config. I'm aware, and that's great, but since those come with their own caveats, yabuts, exceptions, eccentricities and bugs, I don't consider any of those useful solutions to that problem for me.