“We’re doing this to give Web Audio API developers (e.g. gaming, audio applications, some RTC features) more time to update their code. The team here is working hard to improve things for users and developers, but in this case we didn’t do a good job of communicating the impact of the new autoplay policy to developers using the Web Audio API,” says manager John Pallett.
Ayyy death comes a few updates later!
— cabbibo (@Cabbibo) May 16, 2018
Chrome is temporarily reverting the autoplay block for Web Audio with Chrome 66.
— Surma (@DasSurma) May 15, 2018
Not all the games had the same fate. Users could re-enable the audio of some HTML5 games by interacting with the game’s canvas via a click-to-play interaction. On the other hand, some older games were coded with such policy, thus remained muted. The developers will reapply the same policy to the Web Audio API in Chrome 70.