Live data from Hacker News

Firefox 66.0.4 is out, fixes disabled add-ons

ftp.mozilla.org

171–180 of 392 posts

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#171

Earlier quoted context omitted.

Yeah, I gave Firefox a second chance with the quantum updates but, I ran into all the same performance issues I’ve associated with Firefox since version 3

If you used addons in all tests, and/or have ever opened about:config, consider creating a fresh profile without any addons and leaving the settings at the defaults. If you still see problems after a week, that would confirm it’s Firefox rather than whatever third-party modifications you and/or your addons are making to the browser. For example, one of the popular cargo-cult ‘fixes’ for the addons issue instructs Fir…

I saw this in Vanilla Firefox: no addons/no tweaks

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#172
post #28
post #18

Earlier quoted context omitted.

By relying on opt-in you won't test whether a feature actually works for the average user, so if you don't test it, you might roll something useless/confusing/actively harmful out to all of them instead of just a few.

Exactly. The recent Windows 10 update fiascos demonstrate this perfectly: they are opt-in (Insider program) and there were too few users experiencing the bugs to overcome the noise of those who weren't. You need a truly random sample.

So instead of having enough voluntary or paid testers to detect catastrophic, file deleting bugs in a new version, your solution is to just roll out the new changes to random users expecting a stable system?

Something went terrible wrong somewhere, that we got to this.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#173

Did this issue cause all add-on data to be wiped? After updating to 66.0.4, all of the containers I'd created with the multi-account containers add-on were gone and replaced with what appeared to be a default set of containers. I spent a lot of time setting that up—is there no way to get it all back if I don't have some sort of manual backup? And if not, what files do I need to manually back up to make sure I don't l…

Yes, the "Firefox Multi-Account Containers" was unfortunately reset for me too.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#174
The fix doesn't seem to work if you've been using Firefox Beta (67.0b16), or if you then install Stable (66.0.4) and sign in to sync - all addons are still marked as "legacy" and not enabled.

However, if you find each one in the store and (re-)install them - they work again and their data is back intact as expected.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#176

Earlier quoted context omitted.

> It's just the usual tug of war between developers and users for control of the computer. And the annoying part of this being developers who act as if they do not understand (or just brush off) the concerns that the users have. Like, people want control over their own machines. How is that hard to understand?

Because functionality like that can be used to enable/disable features outside of tests as well. For example gating new things which could become a stability issue. Sometimes it's a choice between control or no control. Sometimes it's between your browser crashing or not. The power users will care about control, but the general population of users not really.

> For example gating new things which could become a stability issue.

And yet we were somehow able to ship stable software to millions of people in the days before telemetry/studies. What telemetry/studies truly provides is offloading QA costs to users.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#177
post #158

Earlier quoted context omitted.

uBlock Origin, AdBlock Plus, and other random flavor-of-the-year ad blockers are IIRC the #1 contributor to Firefox slowness, resource usage, and crashes for some years now. They are key examples of “expert user footguns” and I shudder to think how many users are incapable of repairing their browser when damaged by one or more of these addons. Yes, they can reduce bytes over the wire, but they do often come at the co…

Please provide a source that uBlock Origin is the #1 contributor to Firefox slowness, resource usage, and crashes.

I have only my memories, which is what IIRC means: “if I remember correctly”. A few seconds of searching offers no better answer, so you’ll simply have to downvote me and move on.

(For those who want to investigate further, I believe it was about a year ago and would have been on planet.mozilla.org at the time. No, I didn’t post it to HN because I don’t usually consider anti-adblock positions to be safe to discuss here.)

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#178
post #175

So nothing for those of us still running 56 beause Quantum trashed our extensions (and there are still not equivalent availale)?

Why on earth are you running such a massively outdated browser? You should at least switch to pale moon, basilisk, or another maintained browser. God knows how many vulnerabilities in the wild there are in 56.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#179
post #88

Earlier quoted context omitted.

I never did opt in. SO if it's not the default setting, it must have been off.

They made it default. It's called Normandy.

A place most people associate with the largest amphibious invasion in history seems a curious choice of codeword.

Re: Firefox 66.0.4 is out, fixes disabled add-ons

#180
post #3

A good outcome of this certificate fiasco is that many firefox users learned about the "studies" and "Normandy" brain-damage and promptly disabled them.

> A good outcome of this certificate fiasco is that many firefox users learned about the "studies" and "Normandy" brain-damage and promptly disabled them.

I'm actually curious about how the common user reacted to this. There isn't a clue about this on (1) the add-on page, (2) Mozilla's home page, (3) no emails sent out (I get plenty of other emails from Mozilla).

Currently, when you try and (re)install an "unsupported" add-on, you get a cryptic message stating: "Download failed. Please check your connection."

So the only communication from Mozilla is that it's my fault and I need to "check" my connection.

Honestly... there's so much fail here - even at the communication level.

Post reply on HN