Published: Wed, May 16, 2018
Electronics | By Kelly Massey

Google Rolls Back Chrome Browser Update That Broke Web Games And Apps

Google Rolls Back Chrome Browser Update That Broke Web Games And Apps

With the release of Chrome 66 in April, Google clamped down on lots of websites that tried to play video and audio automatically, but the browser doesn't always block autoplay. Google now plans on re-introducing the restrictions in Chrome 70, but the Chrome team is looking into other options as well.

Unless users had whitelisted a site or previously interacted with it, Chrome's blocking feature stops one of the most irritating elements of web browsing: the sudden playing of loud videos.

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. The update rendered those games unable to play sound. But the feature reportedly also silenced the audio in web-based games.

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.

Google didn't immediate respond to a request for comment.

AK Steel Holding (AKS) Shares Bought by Focused Wealth Management Inc
When a short-term moving average crosses above a longer term moving average, this indicates an upswing in the market. Although stock's historical performances are key to consider, don't invest (or not invest) based exclusively on it.

In its Chromium Bug Tracker (via Engadget), Google said it is has now made a decision to temporarily remove the auto mute Web Audio API.

Chrome version 66 introduced new rules which would automatically mute autoplaying ads and videos that tend to be quite annoying and often end up pushing users to ad blockers which is not good for both Google and its publishers.

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.

One of Google's project managers for Chrome, John Pallett, said: "We've updated Chrome 66 to temporarily remove the autoplay policy for the Web Audio API".

Like this: