Latest version of Chrome enables muting of audio in background tabs
Micah Singleton / The Verge :
Context & Ripple Effects
Chrome's move follows its own Dev-build experiment keeping media from autoplaying in background tabs two months earlier — this release turns that passive blocking into an active control, letting users mute a noisy tab themselves instead of relying on defaults.
It is also the first step on a path the corpus traces forward: by 2017 the team was experimenting with permanently muting specific websites, and by Chrome 66 it had moved to blocking autoplay outright — then partially rolling that back when web-game audio broke.
First-order effects
- Users gain a direct switch to silence any background tab without closing it, ending the hunt for which of dozens of open tabs is playing sound.
- Web-based music and podcast players lose the implicit guarantee that background playback is heard — muted tabs still stream, so publishers pay bandwidth for audio no one hears.
Second-order effects
- Once per-tab muting normalizes user-side audio control, Google escalates to default-level suppression — the autoplay-with-sound block in Chrome 66 that disabled audio for many web games and forced developers to update before October.
- That block proved too blunt: Google partially rolled it back under developer pressure, showing that every tightening step now has to be negotiated against the ecosystem of sites built assuming sound plays.
Third-order effects
- If the pattern holds, browsers — not individual sites — become the arbiter of when web audio plays, shifting the burden onto developers to earn audible playback through user intent signals rather than shipping it on by default.
The trend: Browser makers are steadily converting web audio from a publisher-controlled default into a user-granted permission, with each tightening step forcing developer adaptation and occasional rollback.