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 c

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 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".