#1069: Web Audio AudioContext "interrupted" state
Discussions
Log in to see TAG-private discussions.
Discussed
Apr 1, 2025 (See Github)
Matthew is absent.
Jeffrey: Do we want to say anything about WebKit's mixed position?
Hadley: We can note it in the comment. We recognise their decision may have impact on the design.
Hadley to prompt Matthew to post.
Discussed
Apr 1, 2025 (See Github)
*CLOSED
Comment by @matatk Apr 20, 2025 (See Github)
Hi @gabrielsanbrito; thanks for your review request. We are supportive of this work, and ACK that Mozilla is also supportive of it.
We note that WebKit is supportive of the goal here, but haven't yet added a position to confirm that they support it. We recognise that the design may change further as a result. If it changes dramatically, we would like to review it again.
Comment by @gabrielsanbrito Apr 21, 2025 (See Github)
Thanks for the review!
OpenedMar 17, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of AudioContext "interrupted" state.
The Web Audio API is widely used to add advanced audio capabilities to web applications, like web-based games and music applications. One of the API's features is the AudioContext interface, which represents an audio graph. An AudioContext can find itself in one of three states: "suspended", "running", or "closed". Once an AudioContext is in the "running" state, it can only pause media playback by transitioning to the "suspended" state when, and only when, user code calls AudioContext.suspend() on this AudioContext. However, there are situations where we might want to let the User Agent (UA) decide when to interrupt playback - e.g., the proposed "media-playback-while-not-visible" permission policy, the proposed Audio Session API, or during a phone call where the calling application will need exclusive access to the audio hardware. To support these scenarios, we propose adding a new "interrupted" state to the AudioContextState enum.
"suspended" -> "interrupted"
should happen.Further details:
You should also know that...
This specification has already reached consensus in Audio WG and has been merged to the Web Audio specification. Regardless, we would like TAG to do a horizontal review on the "interrupted" state feature.
Thank you!