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 Google Chrome update that broke the audio in a huge number of online games last week has been rolled back. Developers should update their code based on the recommendations at: "https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio".

The original muting of the nuisance videos within Chrome was created to remove one of the annoyances that might have pushed users to install adblocking or other software, something Google wants to avoid as advertising is the primary source of the company's revenue.

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.

"We're doing this to give Web Audio API developers (e.g. gaming, audio applications, some RTC features) more time to update their code", said Google Chrome product manager John Pallett, in a comment on the issue page. Google is planning to re-introduce the update in October along with Chrome 70 update.

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.

The autoplay-video blocker is created to fix one of the greatest problems of the Internet: autoplaying videos on websites. As one of them noted, "Unfortunately, the great majority of existing work will not be updated by October, or ever, and so we still face the effective cultural erasure of those works in October". "You guys definitely have the power to break everyone's work, should you wish to exercise that power, but you do not have the power to make people add workarounds to code that they are not able to alter". Users and developers have listed dozens of web games and audio sites that were broken after Chrome 66. Google now plans on re-introducing the restrictions in Chrome 70, but the Chrome team is looking into other options as well.

"I believe Chrome could find a policy which accommodates developers while still protecting the principle users should explicitly authorize websites to play sound", developer Andi McClure writes in the Chromium thread.