almost everyone by muting sites that would play sound automatically. Unfortunately, it's ended up breaking several projects' audio.
This is a different media release, from Google's own projects. Users were understandably upset, and in response to an overwhelming amount of backlash, Google retained the browser alteration that blocked autoplaying video and audio, but decided to push the feature's application for games and web apps to Chrome 71
What does that mean for you? Chrome 70, is coming around the corner, and it wants to block the autoplaying audio and video. Chrome, 71, at which point developers want to scrambling to figure out a solution.
Ivy Choi spoke to The Verge If you want to start learning which sites are typically used for playing audio and seeks cater to users' experiences, you should not have to frantically search for the mute button on your eardrums unexpectedly by some annoying ad in the future. 70.
There's a list of 1,000 sites that have not been exactly created excited about-especially since the original change was not performed as a major feature in the first place. Instead, it was a meme-tastic, pithy announcement
It's been particularly frustrating for those who make their living through digital media like web games and media projects that all rely on sound. Creators like QWOP's Bennett Foddy, speaking to The Verge, which is particularly frustrated by the way the team has seemed "determined" to take folks who use web audio "by surprise." Others like Stephen Lavelle, creator of the puzzler Stephen's Sausage Roll
Google is currently hard at work on this feature wake when it comes to older games and media projects, where it will allow sound to begin after users have interacted with a page, thus proving their intent and desire to hear sound. Unfortunately, the way Google has gone about this new rollout has not been optimal for creators, which may be more frustrating than being forced to listen to autoplaying ad or video in Chrome … at least for them.
via The Verge