Google Reverts Chrome Desktop In Wake Of Developer Uproar

Google Reverts Chrome Desktop In Wake Of Developer Uproar

Google Reverts Chrome Desktop In Wake Of Developer Uproar

The new functionality was meant to silence auto-playing audio and video in the web browser, but it inadvertently muted audio from many web games and other projects too, with no way to get it back.

According to browser game developers who spoke with The Daily Dot last week, games built using HTML5 game engines like Pico-8, GameMaker, Unity, and Phaser, were affected.

The aim is to give game and audio application developers more time to update their code before reintroducing the policy for the Web Audio API in Chrome 70, due out in mid-October.

This is, apparently, reasonably easy to do; however, some users have complained that, even with several months to act, not every game, art project, or whatever else will be updated.

Chrome begins with a list of more than a thousand sites where Google found that the browser's users typically played audio or video with sound. Google now plans on re-introducing the restrictions in Chrome 70, but the Chrome team is looking into other options as well.

In the Chrome forum, John Pallett explained how Google updated the latest version to "temporarily remove the autoplay policy for the Web Audio API", writing that the change does not affect most media playback on the web, as the autoplay policy will remain in effect for video and audio.

Numerous commenters suggest the Chrome team allow users to opt in instead of enabling the feature by default.

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.

That's not what Chrome's developers intended: the plan was to stop auto-playing vids from assaulting your ears and chewing bandwidth. For now, at least, Google opted for the temporary solution of excluding Web Audio API content from Chrome's autoplay policy. 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". As users continue browsing the web, Chrome updates that list as it learns where you play media and where you don't.

Related news