![disable pop up blocker in firefox 66.0.2 disable pop up blocker in firefox 66.0.2](http://i.ytimg.com/vi/rDY5JS6EqlM/hqdefault.jpg)
- Disable pop up blocker in firefox 66.0.2 install#
- Disable pop up blocker in firefox 66.0.2 update#
- Disable pop up blocker in firefox 66.0.2 code#
- Disable pop up blocker in firefox 66.0.2 windows#
Disable pop up blocker in firefox 66.0.2 install#
Yes yes, I understand that this lockdown was probably to make their browser slightly safer in the hands of clueless people who might gleefully install random third party extensions or follow instructions listed on seedy websites. Perfect emblem of the direction FF is headed. (Plus, they're undermanned over the so for a while they had a hard time keeping some of the rendering backend up to date.) Reluctantly, Back to Firefox I went.īut this is intolerable.
![disable pop up blocker in firefox 66.0.2 disable pop up blocker in firefox 66.0.2](https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/images/2018-01-15-18-11-29-5df364.png)
What the hell is even is Firefox's target demographic any more?įirefox' Chrome copycatting was annoying (I don't want minimalist and 'very slightly faster', I want power and configurability), Pocket was dumb but fine they gotta make money somehow, the loss of legacy extensions (plus the lack of UI customization that came along with with the abandonment of XUL) was *really* annoying and caused me to jump ship to Pale Moon for a while-a neat and ambitious Firefox fork run by some competent and overworked folks-but it became harder and harder to get the extensions I wanted working properly and my enthusiasm for putting in so much elbow grease getting my browser working properly. And I mean if I wanted locked down Fischer Price crap, I'd use whatever the default browser is for my device. It's one of the reasons why I always preferred Firefox over Chrome. The whole POINT of about:config was that it's the ability to peek under the hood.
Disable pop up blocker in firefox 66.0.2 windows#
It's not the fact that they had this glitch that makes me walk away-shit happens, no it's not because they're supposedly letting SJW agendas distract from their coding (jeez, really? I mean I'm all for arguing politics but this is just asinine)-it's that, apparently you can't utilize the about:config workaround on the regular Windows version because you're no longer allowed to mess with those settings. I've been a user for just a few hours now and so far the UX is identical except for the above mentioned improvements. For years and years now, Mozilla has been hellbent on turning Firefox into a shitty Chrome clone and I just do not understand it.Īs far as I can tell, Waterfox is very very similar to the latest Firefox but it doesn't have Pocket, doesn't have a locked down about:config, doesn't phone home user data, supports legacy extensions (which you can get by installing this extension, since Mozilla is no longer hosting the older extensions any more), allows the user to install unsigned extensions, and supports newer extensions very well (unlike the Pale Moon browser, which is interesting and ambitious but it has very spotty extension compatibility). If you don't want to use Firefox for the customability, why the hell do you want it? Seriously now. Which defeats the entire point of Firefox. Seriously, how much crap do we need to take from Mozilla out of loyalty? It wasn't this glitch that was quite so bad as the fact that the about:config workaround didn't work for a lot of people because Mozilla is beginning to intentionally lock down large parts of about:config.
Disable pop up blocker in firefox 66.0.2 update#
UPDATE (): On Sunday Firefox released the second of two weekend updates to address the problem, tweeting that "There are some issues we're still working on, but we wanted to get this release out and get your add-ons back up & running before Monday."Įh, a much better method is to install Waterfox. Getting extensions back for everyone is going to require Mozilla to issue a patch. Because the glitch stems from an underlying certificate, re-installing extensions won't work - if you try, you'll likely just be met with a different error message.
Disable pop up blocker in firefox 66.0.2 code#
Each extension is now being listed as a "legacy" extension, alongside a warning that it "could not be verified for use in Firefox and has been disabled." A ticket submitted to Mozilla's Bugzilla bug tracker first hit at around 5:40 PM Pacific, and suggests the sudden failure is due to a code signing certificate built into the browser that expired just after 5 PM (or midnight on May 4th in UTC time). From a report: Reports are pouring in of a glitch that has spontaneously disabled effectively all Firefox extensions. Did you just open Firefox only to find all of your extensions disabled and/or otherwise not working? You're not alone, and it's nothing you did.