According to manager John Pallett: “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.”
While the transfer ought to restore sound to affected websites for now, there are nonetheless sad builders on the market. As certainly one of them noted, “Unfortunately, the great majority of existing work will not be updated by October, or ever, and so we still face the effective cultural erasure of those works in October.”
Ayyy loss of life comes a couple of updates later!
— cabbibo (@Cabbibo) May 16, 2018
Chrome is briefly reverting the autoplay block for Web Audio with Chrome 66.
— Surma (@DasSurma) May 15, 2018