Google pleased users of the world's most popular web browser last month with the release of Chrome 66, which included a feature that blocked the autoplaying of videos with sound. Sites could only start video and audio automatically if they had a high score on Chrome's 'Media Engagement Index, ' which takes into account how often the user clicks on the site and watches media. The block is still in place for HTML5 video. This change does not affect most media playback on the web, as the autoplay policy will remain in effect for video and audio .
Google has rolled back an update for its Chrome browser after concerns from game developers. The update rendered those games unable to play sound.
The new policy, introduced in April, was created to "intelligently" block unwanted video from playing unless you had either white-listed the site or previously interacted with it.
To be clear, the company hasn't completely removed the new autoplay rules that it introduced with Chrome 66.
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 team here is working hard to improve things for users and developers, but in this case we didn't do a good job of communicating the impact of the new autoplay policy to developers", John Pallett wrote in a developer forum on the bug.
Developers of the web-based games began to complain about broken audio not long after the update originally rolled out, and Google responded that it was investigating.
However, while Google is planning to bring back the policy in October, Pallett noted that Google has yet to solve a "non-trivial user interface challenge with a lot of nuances".