Google partially rolls back Chrome 66's autoplay changes

Google partially rolls back Chrome 66's autoplay changes

The Chrome team said that the changes will not impact the web browser's new feature of silencing Internet videos and audio that have an autoplay feature.

Google has partially rolled back a change made in Chrome 66 that prevented audio from playing in some web-based games. Earlier this year, Google began blocking adverts from websites it deemed to have too many. Google now plans on re-introducing the restrictions in Chrome 70, but the Chrome team is looking into other options as well. "We've updated Chrome 66 to temporarily remove the auto-play policy for the Web", wrote Google Chrome Engineer Abdul Syed in a blog post, publishing a list of changes. For now, at least, Google opted for the temporary solution of excluding Web Audio API content from Chrome's autoplay policy.

The autoplay-video blocker is created to fix one of the greatest problems of the Internet: autoplaying videos on websites.

Google scaled back a new auto-play policy in the latest version of its Chrome web browser, meant to stop unwanted video ads with sound from serving up and playing without notice.

Other comments call for a response from the Chrome development team, particularly with regard to suggestions for modifying the policy to indicate when audio is being disabled, and to enable users to easily switch it back on, either temporarily or permanently. "If you are honest in your claim that the side effects of the policy were unintended and unwanted, you should commit-in clear, straightforward language-to finding other alternatives which do not break vast swathes of cultural work that was developed and distributed on the open web". Pallett writes that Google is "still exploring options to enable great audio experiences for users" but notes that "this is a nontrivial user interface challenge with a lot of nuances". Some feel that Google is restricting the spirit of a free and open web buy forcing their standards on the world's most popular browser. "Interestingly, another developer Benji Kay responded to Pallett's post, by saying, "Simply delaying the enacting of this policy doesn't solve any of the major concerns" with its contents".