There's probably an advanced setting buried somewhere if you _really_ want to turn that behavior off, but why would you?
There's probably an advanced setting buried somewhere if you _really_ want to turn that behavior off, but why would you?
- Browser updates often carry more than just security fixes, which may or may not be wanted by the user
- Background updates make it less likely for the user to know why their software is being updated
- The user may have a legitimate reason for sticking with an older version of a piece of software
- Most browsers already show the user when a new update is available. For users interested in all of the latest security updates, they can read about what these are and simply download the update right away
It's a good thing that this feature can be configured.
https://www.ghacks.net/2021/04/28/mozilla-is-working-on-fire...
"Bother the user with a dialog that lets them shoot themselves in the foot every time there's an update." isn't a good solution to that problem. Firefox's Extended Support Release[1] is a better one, but even with that users will need to accept a feature update eventually.
There may be legitimate situations where it does make sense to turn off automatic updates (that's why the option is there), but they're very niche and require a lot of expertise to pull off without compromising security. Well designed software should intentionally make it hard to disable critical security features without knowing what you're doing.
I also don't think informing users about the contents of an update usually meets the bar where it is "absolutely necessary" to interrupt them just for that. Unless your update is about to break something important (which you should certainly avoid if at all possible) patch notes shouldn't be required reading.
You can create a policy for it
{
"policies": {
"DisableAppUpdate": true
}
}
Create a JSON file called `policies.json` and paste the above code into it. Then place that JSON file in a folder called `distribution`. Then make sure to place the `distribution` folder in the application folder of the browser.Not sure why you want to do that, as updates are essential for security. Apparently it's for 'enterprise organizations' who probably want to limit the chatiness of their network and reduce latency.
You could also install Firefox ESR which doesn't ping Mozilla for updates nearly every 10 seconds.
There's an economically powerful EU country that has a lot of train travel and not so many trains having great internet access. This was my commute life for a few years.
I'd stop right at "auto-installation of updates with security fixes is the correct default", because that's very solid.
And updates that don't install until you open the program. Sparkle apps on macOS do this and it drives me nuts.
If you're going to update or want my attention about a new thing, have a red dot somewhere that is not conspicuous. Don't get in the way of a user trying to be a user. This is one thing that the Slack app gets absolutely right.
Firefox toes the line. New versions occasionally pop up a new window. It's easy to close but jarring. At least the updates happen mostly transparently and tend to not radically change appearance or behavior. They're bringing this experience to Windows now.
Because updates can introduce breaking changes. And potentially new security vulnerabilities.
but you can flip the switch if you really must.
Linus calls this trading old bugs for new bugs, and is vehemently against introducing commits that may introduce new bugs, no matter the severity of the bug that the commit squashes.
Most people don't.
For the rare people that do (probably 100 on the entire planet), they can disable the automatic updates and do it manually.
I have no problem with automatic updates I can disable.