Changes to Chrome OS’s release cycle
blog.chromium.org
blog.chromium.org
Sounds funny, but stuff happens :)
Seems like a good thing to match the chrome cycle.
[aboutchromebooks](https://www.aboutchromebooks.com/news/lacros-vs-chrome-and-c...) has a nice explanation as well.
The reasoning I've read behind it is this will allow updates to continue for the browser much longer (probably more important!) than the cycle of the OS which has a much more finite support window.
Plus, certain financial institutions require me to go through lengthy 2FA again because I'm no longer using the "same" browser. (This is the fault of the institutions, not Google.)
Again, auto-update is great, but there are still these little kinks that need ironing out... after so, so many years.
I was so hoping you were right! Oh well...
The location permissions system preferences behavior changes in more macOS updates than not. The current system hasn't been around for that long.