Clear white screens in Chrome left numerous IT administrators and clients confounded
Google left a huge number of machines in organizations with broken Chrome programs this week, following a quiet test change. Business clients getting to Chrome through virtual machine conditions like Citrix continued seeing white screens on open Chrome tabs, blocking access to the program and leaving it absolutely inert. It left numerous IT administrators befuddled over the issue, as organizations ordinarily oversee and control Chrome refreshes.
After protests, Google had to uncover it had propelled an “experiment” on stable adaptations of Chrome that had changed the program’s conduct. The trial was made quietly, without IT administrators or clients being cautioned about Google’s changes.
Google had just flipped the switch on a banner to empower another WebContents Occlusion highlight that is intended to suspend Chrome tabs when you move different applications over them and lessen asset use when the program isn’t being used.
“The experiment / flag has been on in beta for ~5 months,” explained David Bienvenu, a software engineer at Google, in a Chromium bug thread. “It was turned on for stable (e.g., m77, m78) via an experiment that was pushed to released Chrome Tuesday morning. Prior to that, it had been on for about one percent of M77 and M78 users for a month with no reports of issues, unfortunately.”
Google moved back the change late on Thursday night, following numerous reports from organizations with a large number of clients influenced. “I’ll rollback the launch of this experiment and try to figure out how to deal with Citrix,” noted Bienvenu in the bug string.
“This has had a huge impact for all our Call Center agents and not being able to chat with our members,” explained a Costco IT admin in the Chromium thread. “We spent the last day and a half trying to figure this out.”
One IT administrator that cautioned The Verge to the issue said “we felt that this is a shady thing that Google can update Chrome silently without announcing anything and can impact 100,000+ people on a whim.” Those worries are reflected by several answers on Google’s help gathering, the bug tracker string, and on Twitter and Reddit.
It has left IT administrators furious that they’ve burnt through important assets and time on attempting to fix issues in their condition, and inquiries over why Google chose to roll out a quiet improvement to Chrome in any case. “I am stunned by your response,” said one IT admin in response to Bienvenu’s confirmation on the issues.
“Do you see the impact you created for thousands of us without any warning or explanation? We are not your test subjects. We are running professional services for multi million dollar programs.”
People’ve connected with Google for input on the Chrome issues, and people’ll refresh you in like manner.