Google's latest Chrome update, which blocks autoplaying videos, has also disabled audio for many web-based games; Google says developers should update
Phillip Tracy / The Daily Dot :
Context & Ripple Effects
Google spent late 2017 telegraphing this change: after experimenting with per-site muting controls [[a:921739]], it announced Chrome would stop autoplaying videos with sound from January 2018 [[a:922354]]. What the rollout exposed was collateral damage the announcement never priced in — web-based games that load audio alongside video got silenced too.
First-order effects
- Web-game developers whose titles lost audio must rework how their code triggers sound, under Google's instruction to update rather than any change to the policy itself.
- Players of affected browser games are the immediate casualties, stuck with silent games until each developer ships a fix.
Second-order effects
- Google's follow-up move — a partial rollback of the autoplay block in Chrome 66 while keeping an October deadline for developers [[a:929593]] — shows the company absorbing developer backlash by carving exceptions instead of abandoning the policy.
- Other sites relying on autoplaying media now face the same forced migration, since Google has demonstrated it will ship default-breaking changes and let the ecosystem scramble.
Third-order effects
- If the pattern holds, browser vendors become de facto standard-setters for web media behavior, with developers building to rolling vendor deadlines rather than stable specifications — and platform owners learning to pair aggressive defaults with grace periods to blunt backlash.
The trend: Browser vendors are asserting control over web media defaults through shipped-then-adjusted policies, turning web development into a rolling compliance exercise against vendor deadlines.