Is this something new admins just have to learn about and be worried about or is there a way to avoid it? There’s a little good news, but mostly bad news. So, it turns out Google can just decide to subject every user to new features without them even knowing. While some users might be able to jump to another browser (provided the web application they use is multi-browser), this isn’t always an option for tightly controlled workplaces. Unfortunately, the experimental feature didn’t work well for virtual environments and left workers staring at blank tabs if they used RDS or Citrix (we didn’t happen to see any mentions of this happening in VMware Horizon environments). (It’s not clear why Google didn’t do a staged rollout.) One comment in the thread mentioned having issues with Chrome before last week and wondered whether they were part of the 1%-it’s not clear. It was already live on about 1% of users’ devices and as Google didn't notice any complaints or issues, they went ahead made it live on the stable version of Chrome. The feature had been in beta for about five months, according to the Chromium bug thread. Instead, Chrome would unload the tab entirely when it sensed another app in active use. The feature is designed to reduce resource usage when not in active use (which given how resource-hungry Chrome is, is a good idea), it just didn’t work as intended. Google decided to enable an experimental flag called WebContents Occlusion to stable Chrome versions (77/78)-spoiler: it didn’t go very well. Let’s look at what happened and whether there’s anything admins can do going forward to prevent this (if it’s preventable).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |