Earlier quoted context omitted.
Resolved as in you're opted in to studies?
I never did opt in. SO if it's not the default setting, it must have been off.
Firefox 66.0.4 is out, fixes disabled add-ons
101–110 of 392 posts
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#102Earlier quoted context omitted.
I don't see the purpose. There seems to be an assumption that A/B testing is inherently bad, therefor should be opt-in. A/B testing is necessary for stable rollouts, that much seems self evident. So what is the evidence that A/B testing is harmful to users?
It isn't A/B testing that is bad, it is running and/or modifying stuff in the user's computer without their knowledge that is bad. If a site modifies some part of their layout or whatever isn't bad, but a browser installing addons or changing settings to see if it will crash is bad.
Wouldn't it be more irresponsible to deploy to every user without first testing it out?
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#103I'm sorry to break it to you Chrome fanboys but it'll take a lot more than a minor extensions goof up (that was fixed in a day) for me to switch my browser.
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#104I don't understand why renewing the certificate wouldn't fix the issue ? How does the 66.0.4 fix the problem exactly ?
It's a signing certificate that is built into the browser to verify add-ons, not a normal TLS certificate that they can just update on a web server. The change basically just imports the new certificate into the database: https://hg.mozilla.org/releases/mozilla-release/rev/848b1502...
My extensions on FF have not stopped working but I hadn't restarted the browser in that interim
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#105Earlier quoted context omitted.
It's a signing certificate that is built into the browser to verify add-ons, not a normal TLS certificate that they can just update on a web server. The change basically just imports the new certificate into the database: https://hg.mozilla.org/releases/mozilla-release/rev/848b1502...
> It's a signing certificate that is built into the browser to verify add-ons, not a normal TLS certificate that they can just update on a web server. Ah, so that's why. Thanks. What was the signing certificate validity period ?
Not Before: Apr 4 00:00:00 2015 GMT
Not After : Apr 4 00:00:00 2025 GMTRe: Firefox 66.0.4 is out, fixes disabled add-ons
#106Earlier quoted context omitted.
Firefox on mac used to be like that, but recent versions (last year or two) haven't had that issue You're probably being downvoted for negging others' beloved browser
I gave it a spin about 4 months ago and stuck with it for about 2 months and was still having the issue. A Mozilla employee pointed me here to watch for updates on the issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 Edit: Also relevant: https://github.com/servo/webrender/issues/3115
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#107I was already a bit mad at them for removing RSS support and claiming their proprietary service that's built in is an alternative, now their proprietary service keeps working (presumably, I didn't use it but it's not an addon so I doubt it's signed the same way) and I can't use the RSS addon. I know this was a mistake, but I can't help but be mad that their proprietary built in stuff effectively gets a free pass and…
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?
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#108>open ff >lastpass gone >google error messages >please update ff >update >browser works I'm sorry to break it to you Chrome fanboys but it'll take a lot more than a minor extensions goof up (that was fixed in a day) for me to switch my browser.
Re: Firefox 66.0.4 is out, fixes disabled add-ons
#109Earlier quoted context omitted.
xpinstall.signatures.required = false worked for me on android
Yeah, this also worked for me on Android. Not sure why the downvotes.