4 ms·
I wonder if you'll have to remember to do this after each update, like you have to do for most of Chrome's unwanted and unwelcomed features.
by stronglikedan 2y ago
I wonder if you'll have to remember to do this after each update, like you have to do for most of Chrome's unwanted and unwelcomed features.
- Ennea 2y agoProbably not. These settings have been around for a long time already anyway, and they never get overwritten once set, at least in my experience.
- wewxjfq 2y agoWhen you haven't used Firefox for a while it shows a prompt that tricks you into resetting your profile.
- atomicfiredoll 2y agoOnly time will tell, but I don't think I've ever had that issue with Firefox so far.
- saganus 2y agoApparently not, at least for this update. I had the settings disabled, then updated to the latest version ("126.0 (64-bit)") and settings were kept disabled. So at least for now it looks like it respects your current settings.
- hagbard_c 2y agoIt might be possible to disable this feature through a policy file [1] just like other features can be disabled, e.g. here's how to disable auto-update: { "policies": { "DisableAppUpdate": true } } Create a text file named policies.json in a directory named distribution inside the Firefox installation directory. In my case that ends up looking like this: /opt/APPfirefox (package root) /opt/APPfirefox/firefox (currrent nightly) /opt/APPfirefox/bin/firefox-127.0a1 -> /opt/APPfirefox/firefox/firefox-127.0a1 /opt/APPfirefox/distribution/policies.json The browser sees this file and abides by its contents. Open about:policies#documentation in Firefox to see which policies can be configured this way. [1] https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson https://support.mozilla.org/en-US/kb/customizing-firefox-usi...
- sunaookami 2y agoThey already did this way back with their other telemetry stuff. You had to disable it through about:config and then Mozilla introduced new flags/renamed them and even added a flag if you have disabled telemetry that you had to disable again manually.