Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Tell HN: Legacy WebAudio content will break in Chrome 70. Parent comment
> 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".
> 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".