Instead, you'll see a scarier, red "This has been disabled" message. Since FF 53 doesn't expect to have add-on signing disabled, it doesn't have the yellow "warning" text that FF 52 ESR does for an "unverified" add-on.
(I put it after code, but it will probably work before it too.) The workaround at the link can be combined with fix for re-enabling SSUAOs in Firefox 52:įirst, follow the instructions there then add this JavaScript to the config.js file you just created: Luckily, there is a workaround, but it's a bit more complex than just setting a preference. You can even hide the warnings with an add-on like Classic Theme Restorer.īut FF 53 is a "stable" release, and doesn't work in stable FF releases. The unsigned add-ons will produce warnings in the about:addons page, but they work.
You simply set the about:config preference to false and you're good to go. In FF 52 ESR, unsigned add-ons aren't much of a problem. (A couple were add-ons that were originally signed, but from which I had removed the signature in order to implement some hack.)
The biggest example was the legacy version of uBlock Origin, which I use because it offers more privacy protections than the WebEx version does on FF 52 and 53. Usually these were legacy add-ons that continued to be maintained after Mozilla banned pre-WebEx add-ons, and thus could no longer get Mozilla to sign them. When I tried out FF 53, I discovered that some of my add-ons got disabled.
0 kommentar(er)
