News for hackers. Stuff that matters.
Re:Tell HN: Legacy WebAudio content will break in Chrome 70 by fenomas on Tuesday September 25, 2018 @11:18AM (#18067009)
I'm no expert but I believe it follows standards. Quoting the spec:

> Note: For example, a user agent could require that an AudioContext control thread state change to running is triggered by user activation

https://www.w3.org/TR/webaudio/#allowed-to-start

That's essentially what the Chrome policy does - it changes when the AudioContext moves from the "suspended" state to "running".

Re:Tell HN: Legacy WebAudio content will break in Chrome 70 by gsnedders on Tuesday September 25, 2018 @11:25AM (#18067107)
That's a non-normative note, the normative statement that allows the behaviour is the paragraph before that.