Intent to Implement and Ship: OfflineAudioContext.startRendering returns a promise
Raymond Toy
Contact emails
rt...@chromium.org, hong...@chromium.org
Spec
http://webaudio.github.io/web-audio-api/
Summary
The WebAudio spec requires startRendering to return a promise which will resolve to a buffer containing the rendered data. Previously the startRendering method for an OfflineAudioContext returned nothing, and expected the the user to have an oncomplete event handler to get the desired rendered audio data.
Motivation
The W3C spec requires startRendering to return a promise. See also https://github.com/WebAudio/web-audio-api/issues/252 for addtiional information.
Compatibility Risk
There is no compatibility risk. This change is backward compatible because the oncomplete EventHandler is still available and still works the same way.
Ongoing technical constraints
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
OWP launch tracking bug?
Link to entry on the feature dashboard
None yet, but one will be added soon.
Requesting approval to ship?
Yes.
Philip Jägenstedt
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
