Among the sticking points has been Chrome's automatic updating mechanism, which some decried for force-feeding unwanted changes, or for delivering those changes at speeds too quickly for customers to absorb.
The browser periodically checks for updates; Google's own documentation, which is often left long out of date on the firm's site, says in one place it does so every 23 hours and 20 minutes.
When Chrome does detect an available update, it downloads the new code and preps it for installation, although that latter step doesn't begin until the user starts or restarts the browser.
But not every copy of Chrome receives an update as soon as Google issues one.
Officially, Google recommends that users frequent this blog to track just-issued updates, including the security-only fixes that pop up at irregular intervals between each polished edition's arrival.
Removing the responsibility for updates, particularly security updates, from the user has been a decades-long theme in software for a good reason, as it results in a higher percentage of up-to-date devices.