![]() ![]() And now it’s known that all future versions from 41 will be infected with this retarded mandatory signing. But Firefox with multiprocess will be released only around Firefox 45. The reason why I most hate it is that I wanted to have a Firefox with multiprocess (Electrolysis) support. I hope the Firefox 38 ESR will not get the mandatory signing, because I want to use the latest Firefox 38 ESR that is planned to be released. I will stay with the latest Firefox 38 ESR that doesn’t have mandatory signing. The only good Firefox versions have ever been released are the Firefox 17.0.11 ESR, and Firefox 38. And this way I can install them even if they’re removed from the official addons page. xpi addon files to backup them on my PC and my backup DVDs. It’s even worse than the horrible Australis UI. Mandatory signing is the worst thing that Mozilla have ever done. The company flatters ignorance and prevents users’ improvements that another policy would trigger. I know, a user will be able to ask for an add-on to be “signed” by Mozilla, but how long will it take? And for a tweaked add-on, how long again? I will not endure this, certainly not.Īs I understand it, Mozilla’s opinion about an average user is to consider him in kindergarten. I have now 77 add-ons, some that will never be signed, some that cannot be signed. Cyberfox’s developer is for the time being unsure about the way he intends to handle this new add-on signing requirement once it will be de facto mandatory in Firefox (41) but as far as I’ve understood it, he claims it is technically possible.Īll I can say is that if Cyberfox does not offer any means to circumvent this add-on signing process, I will be leading to another default browser, Pale Moon most likely, but not for sure again because of the add-ons’ limitations, though in terms of availability. My default browser is at this time Cyberfox, a Firefox fork as we know. How to disable the add-on signing enforcement ![]() Mozilla plans to make the override switch available in Firefox ESR currently for the time being (meaning that the override will remain and not be removed). If that is the case, it would hit when the ESR channel reaches version 45. ![]() It is unclear right now if the rule will be enforced for Firefox ESR as well. The override is no longer working and there is no option available to install unsigned extensions on Stable or Beta Firefox versions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |