Saturday, 22 September, 2018

This Well-Meaning Chrome Update Broke Several Apps and Games

Google Chrome Autoplay Policy Delayed After It Breaks Some Games Web Apps This Well-Meaning Chrome Update Broke Several Apps and Games
Sherri Watson | 17 May, 2018, 01:20

Unfortunately, older games and those that weren't coded with such policy remained irrevocably broken, no matter what Chrome options users tried to modify in their settings sections. However, the policies were reported to have a negative effect on and other Web experiences like games and Web apps.

Google has partially rolled back an update to its popular Chrome web browser, after discovering that changes introduced to block auto-playing media were wreaking havoc on the browser-based gaming scene.

Google has had to temporarily break one of Chrome's newest features because it was proving more troublesome than the annoying problem it was supposed to tackle.

The developer community has made their frustrations clear and the hiccup has found its way to the CRBug tracker and the folks at Chromium have taken notice.

In its Chromium Bug Tracker (via Engadget), Google said it is has now chose to temporarily remove the auto mute Web Audio API. Affected developers will have until then to add a few lines to their code, thus re-enabling the auto-muted audio when a user first interacts with the page. It will return with Chrome 70 in October. It seems some games are not functioning properly, even after being whitelisted and so in the new version Google will be rolling back that change to give devs time to change how their games work.

By automatically pausing Web Audio objects when a webpage is launched, the update earlier this month was meant to help silence ads that seemingly begin barking at you when you visit some sites. "The team here is working hard to improve things for users and developers", he said, "but in this case we didn't do a good job of communicating the impact of the new autoplay policy to developers using the Web Audio API".

Google's Chrome team recently said that it has updated the mobile web browser to temporarily put on hold the autoplay policy for the apps, games, and RTC features using the Web Audio API.

The "more time for developers" angle is an - ahem - interesting one, because Chrome 66's beta debuted on March 21, 2018 and discussion of its features played out for several months before that date.