Google partially rolls back autoplay-blocking update in Chrome 66 after it disabled audio for many web-based games, urges developers to update before October
Google is partially and temporarily rolling back a recent Chrome change that blocked autoplaying audio, after web developers complained …
Context & Ripple Effects
Google has been tightening Chrome's autoplay policy for years — it first signaled the shift in September 2017 and shipped blocking of autoplaying content with sound in the Chrome 66 release this April. Within weeks the policy collided with reality: as reported last week, the change had silently disabled audio for many web-based games built on older media APIs.
First-order effects
- Web game developers whose titles lost sound under Chrome 66 get temporary relief as Google partially restores autoplay audio while they migrate to the new APIs.
- Developers now face a hard deadline — October — after which Google's original autoplay-blocking behavior returns and unmigrated games break again.
Second-order effects
- Game studios and engine makers must prioritize updating their audio pipelines ahead of content sites, since interactive media is where the policy's collateral damage is concentrated.
- The episode hands browser rivals a talking point on compatibility risk, pressuring Google to pair future policy changes with longer migration windows or better developer tooling.
Third-order effects
- If Google holds the October line, browser vendors' power to unilaterally reshape web media behavior — with rollback only as a pressure valve — becomes the de facto governance model for how the open web plays sound and video.
The trend: Browsers are asserting unilateral control over web media defaults, forcing developers onto new APIs on vendor-set timelines even when the transition breaks working software.