Earlier quoted context omitted.
Well, it's not like they're hoping it will crash. Presumably they're hoping it won't . Wouldn't it be more irresponsible to deploy to every user without first testing it out?
that's what the stable/experimental channels are for - a user who don't want to be tested on (such as a business user) can easily be sure that they are getting a stable release and their settings won't update under them. Experimental/beta channels can have these changes pushed to it, since that's implied by the name, and those people who like living on the edge of new features do so knowingly. Let the users control t…
Firefox 66.0.4 is out, fixes disabled add-ons
251–260 of 392 posts
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#252Earlier quoted context omitted.
Note that these statistics would, presumably, exclude all users who disable telemetry in Firefox. Since many of those outraged at the interruption to addons seem to overlap frequently with those who object to and disable telemetry and studies on principle, their departure over this incident could well have no impact whatsoever on the metrics you linked above. It must be a nightmare for the Firefox team to have a mino…
Who's fault is that, at the end of the day? Mozilla didn't have to structure their addon system in such a way that their (in)actions could disable the addons of every Firefox user on the planet . Mozilla did not have to abuse the studies mechanism (also on by default) to ship a workaround. Mozilla did not have to disable the option that would let me work around this problem by myself (which is going to cause me no en…
Might I interest you in Internet Explorer 6?
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#253Earlier quoted context omitted.
How do you do this?
From an updated Firefox navigate to Preferences -> Privacy & Security -> Security -> Certificates -> View Certificates Now find: Mozilla Corporation signingca1.addons.mozilla.org Select signingca1.addons.mozilla.org and then choose export. This is what you would import into the older version of Firefox.
Is there a way to report this without spending hours to register at Bugzilla and file a proper bug report?
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#254About time. Embarrassing bug. The only reason i didn't permanently swap browser is because of the lack of alternatives since none has the functionality I apply through the addons.
I switched to the Dev build[1] with 'xpinstall.signatures.required = false', and now that it's fixed I don't know if I'll go back. There seems to be a bunch of new features in Dev that I assume will arrive in Firefox eventually, but everything else being equal, I think I'll stick with it. I'll probably turn 'xpinstall.signatures.required' back to true though. [1] https://www.mozilla.org/en-US/firefox/developer/
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#255Earlier quoted context omitted.
Yeah, this also worked for me on Android. Not sure why the downvotes.
You're better off waiting a few more hours that disabling important security features.
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#256Earlier quoted context omitted.
In this case, I was more insecure being subjected to advertising networks (and the malware carried on them) because of Firefox's mistake which meant I wasn't able to load ublock origin. I'm also not sure how many of those "security patches" are intended to make my browsing experience safer, or simply meant to implement bizarre policies that might blow up in my face at any time (as this certificate issue has). It's a…
This "bizarre policy" was software signing, which is in fact a security feature. I don't understand what "getting their act together" means here, when you're posting it on an announcement that the problem has already been fixed. Should Firefox proactively remove all security features that risk ever posing some modicum of inconvenience to users? Because that would be... all of them.
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#257About time. Embarrassing bug. The only reason i didn't permanently swap browser is because of the lack of alternatives since none has the functionality I apply through the addons.
I switched to the Dev build[1] with 'xpinstall.signatures.required = false', and now that it's fixed I don't know if I'll go back. There seems to be a bunch of new features in Dev that I assume will arrive in Firefox eventually, but everything else being equal, I think I'll stick with it. I'll probably turn 'xpinstall.signatures.required' back to true though. [1] https://www.mozilla.org/en-US/firefox/developer/
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#258This is pretty bad for Firefox. I wonder how much people straight up & left for Chrome as a result of it.
I personally found the issue trivial, my main addon is ublock origin. There was a workaround using about:debugging and installing UBO on there which worked so it's not like the fix was a long process.
Being committed to a single browser, if anyone was using firefox for as long as me, I can't fathom someone leaving their main browser over something like this. I haven't been using it for THAT long but what if Chrome did something like this too? Then they'd move to another browser that's not FF/Chrome?
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#259Re: Firefox 66.0.4 is out, fixes disabled add-ons
#260Earlier quoted context omitted.
I use containers too. I didn't loose any data after I enabled dev mode and added the extension back. Perhaps you removed the existing extension first and lost data that way?
It's odd - on my laptops, my multi-container settings were preserved, but I opened firefox on my desktop last night and they had vanished. I did not remove any add-ons myself.
Only difference is that I restarted the desktop Firefox and also enabled Shield studies to get the temporary fix. On the laptop I just upgraded to 66.0.4 and only then restarted it.