hong...@chromium.org, mjwi...@chromium.org, sinaf...@chromium.org
None
https://github.com/WebAudio/web-audio-api/pull/2580
Introduces an event listener on AudioContext to notify developers of audio device or rendering system failures.
Currently, developers lack visibility into the success or failure of their AudioContext, whether during its creation or while actively rendering audio. In the event of failure, web applications misleadingly continue to function as if audio playback is proceeding normally.
The AudioContext.onerror event listener allows web applications to proactively respond to and manage device or rendering failures.
https://github.com/WebAudio/web-audio-api/issues/2567
http://github.com/w3ctag/design-reviews/issues/950
Resolved
None
Gecko: Positive (http://github.com/mozilla/standards-positions/issues/1016)
WebKit: Defer to Audio WG (https://github.com/WebKit/standards-positions/issues/340)
Web developers: Positive (2020 Developer Survey)
Other signals: N/A
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
No, AudioContext failure scenarios cannot be tested in WPTs. Chromium-internal tests will fully exercise this scenario.
None
AudioContextOnError
N/A
False
https://launch.corp.google.com/launch/4317143
M127
https://chromestatus.com/feature/5113439453446144