Skip to content

Consider interrupted case on error handling section #2633

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

gabrielsanbrito
Copy link
Contributor

@gabrielsanbrito gabrielsanbrito commented Apr 11, 2025

This PR defines what should be done if an error occurs while an AudioContext is interrupted.


Preview | Diff

@hoch hoch added the Agenda+ Should be discussed at the next WG meeting. https://speced.github.io/spec-maintenance/about/ label Apr 17, 2025
@mjwilson-google mjwilson-google merged commit 7f58ac7 into WebAudio:main May 15, 2025
1 check failed
@mjwilson-google mjwilson-google removed the Agenda+ Should be discussed at the next WG meeting. https://speced.github.io/spec-maintenance/about/ label May 15, 2025
aarongable pushed a commit to chromium/chromium that referenced this pull request May 16, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
This is a follow-up to https://crrev.com/c/6441740

Now that the spec change has been merged:
WebAudio/web-audio-api#2633

we should do the same thing as the running state when a render error
occurs.

Change-Id: I818de64edcd21b6a771befe57eba884a429a67fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6555082
Reviewed-by: Gabriel Brito <[email protected]>
Commit-Queue: Michael Wilson <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1461159}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants