This message was deleted.

Yes i can confirm we're battling it right now, helpdesk lit up Some talk on the IRC channel.

That's two versions in a row. Nice

Thnks for this heads up.

It's not just 78. We're on 76 and 77, and have the problem in both.

🤦‍♂️

https://bugs.chromium.org/p/chromium/issues/detail?id=1024837 if you've not seen it already. Guess this guy is gonna get some stick!

Ouch

An update was released but still no mention of a fix. https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller&n=10000

@Jonathan Pitre here is a link to Chromium's bug tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=1024837#c124. There are several "fixes." Disable the flags directly, start Chrome with the --disable-backgrounding-occluded-windows switch, disable all flags / experiments by starting Chrome with the --no-experiments switch. Some / all may or may not work. There are reports both ways, and in the meantime, Google continues to say that the experimental feature is turned off (rolled back) on their end (although comments on the link above seem to indicate otherwise). And one point of clarification - this is not related to Chrome version, so an update to the app will not solve. This was a Google controlled server side flag enabled by Google. The flag is on and enabled in all (current) versions of Chrome, and Google flipped the switch on their end to put it into production.

@Tim Riegler yeah we are using the flag for now. I would love to see an official statement from Google saying it's really fixed.

Having to use switches is an awful solution for anyone not using something like WEM to deploy shortcuts.