Google partially rolls back Chrome 66's autoplay changes

Google rolls back autoplay ban in Chrome 66 after borking web-based games

Chrome is getting too clever for some

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. But the feature reportedly also silenced the audio in web-based games.

The blocking feature, announced in January, aimed to remove loud, sudden and unwanted videos from the web, which automatically played when a browser launched - and also stopped a series of apps and games from playing audio for alerts and other elements.

However, the unintended effect of silencing web games has prompted Google to temporarily remove the autoplay policy for the Web Audio API, which is used by many web games.

Google has tweaked Chrome 66 to make the new feature that silences auto-playing videos less aggressive. This shouldn't affect most audio and videos (included in the audio and video HTML tags), which will continue to be auto-muted, but should ensure the accidentally affected web components are working correctly. The browser began with a list of 1,000 websites where Google found that users typically played audio or video with sound.

The Chrome team admits that it "didn't do a good job of communicating the impact of the new autoplay policy to developers using the Web Audio API".

Europe offers no guarantees but vows to keep Iran deal alive
But Secretary of State Mike Pompeo said Washington was keen to thrash out a more wide-ranging deal with its European partners. "It is going to be very hard for us to preserve the economic benefits of the Iran deal", one senior European diplomat said.

Google is rolling back a recent Chrome browser update that inadvertently broke the audio in many HTML5-based Web games.

Meanwhile, the implementation delay will give "Web Audio API developers for gaming, audio applications, some RTC features more time to update their code".

Have you come across any such unintended consequences on Chrome?

While the original audio policy change blindsided developers, the temporary rollback seeks to give them time to adapt their projects for the coming change but, as some devs pointed out last week, not everyone affected by the change has the ability, time, or resources to go back and retroactively change the code of projects already online.

As per a report in The Verge, a developer named Ashley Gullen had revealed the ways to fix the issue, but Pallett has said that it is a "non-trivial user interface challenge".

Latest News