4 ms·
You bring up a good point. I think the reason I feel this way is that Google's screw ups didn't inconvenience my usage of Chrome, whereas Mozilla's have inconve
by Mirioron 7y ago
You bring up a good point. I think the reason I feel this way is that Google's screw ups didn't inconvenience my usage of Chrome, whereas Mozilla's have inconvenienced my usage of Firefox. What made me initially switch to Chrome was the UI change in Firefox. Years later I thought of swapping back to Firefox and I found out that Firefox doesn't allow me to run my own add ons without their approval.
- eropple 7y ago> I found out that Firefox doesn't allow me to run my own add ons without their approval. This is not and has never been true. What is no longer possible is the ability to sideload extensions outside of the browser by copying files into a directory because that's how dirtbags have stuck extensions that could not be uninstalled into Firefox as part of a third-party app install. Go to `about:addons`, install add-on from file, you're done.
- Mirioron 7y agoAre you sure? Because I just created a barebones hello world. It works fine as a temporary add-on, but I can't install it from the file. Says the add-on is corrupted. Then I downloaded a working add-on. It worked fine when installing from file. I removed the signing information. It installs fine as a temporary add-on, but throws the same error as the hello world. I'm pretty sure that the add-ons need to be signed by Mozilla to install from file.
- commoner 7y agoYou'll need to use Firefox Developer Edition, Nightly, or ESR. Then, go to about:config and set xpinstall.signatures.required to false. https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/#signing-your-addons https://extensionworkshop.com/documentation/publish/signing-... You can then sideload unsigned add-ons by following these instructions: https://extensionworkshop.com/documentation/publish/distribute-sideloading/ https://extensionworkshop.com/documentation/publish/distribu...