[omh]

I've been dealing with this bug for the last couple of days and it's been hugely frustrating.

This was not a new version of Chrome or a software update. None of our software was updated at all (and we spent a long time checking!). But apparently Google have an ability to change a setting and globally affect the behaviour of all Chrome browsers by enabling experimental features.

We carefully manage our software updates and patching so that we can test it and roll back if it impacts the business. Google had been good at understanding "enterprise" requirements - disabling automatic updates, setting policies etc. But this shows that they're really focused on consumers and business users will always be an afterthought.

[staktrace]

As an admin why would you not also run the beta version of the browser in a limited setting? That would have helped you find out about this issue sooner, since the experiment was enabled there for a while.

[yabadabadoes]

I'm sure plenty of admins do, that doesn't mean you will test with the same flags chosen in an experiment it only means you will see changes going into stable permanently enabled a bit early.

My own experience with ChromeOs is that I switch to beta, report bugs via interfaces provided (by Google) and then the chromium team acts surprised when the regression hits stable.

If you ignore signals don't ask for them.

Edit- clarity

[blub]

That's putting it lightly. All your computers have a Google backdoor.

It's not about businesses versus personal users, people are for Google an afterthought, they are mere information generators.