Describe the issue
After OfflineAudioContext.startRendering() finishes and the returned promise resolves, the context transitions to the "closed" state and a statechange is fired. Apparently, all the major browser engines implement this behavior. I personally verified Blink and Gecko, but WebKit also seems to be implementing something similar.
This behavior is not in the specification. The specification only says here that:
- Once the rendering is complete, queue a media element task to execute the following steps:
- Resolve the promise created by startRendering() with [[rendered buffer]].
- Queue a media element task to fire an event named complete at the OfflineAudioContext using OfflineAudioCompletionEvent whose renderedBuffer property is set to [[rendered buffer]].
Where Is It
OfflineAudioContext.startRendering()
Additional Information
You can use this demo page to test it out.
Describe the issue
After
OfflineAudioContext.startRendering()finishes and the returned promise resolves, the context transitions to the"closed"state and astatechangeis fired. Apparently, all the major browser engines implement this behavior. I personally verified Blink and Gecko, but WebKit also seems to be implementing something similar.This behavior is not in the specification. The specification only says here that:
Where Is It
OfflineAudioContext.startRendering()
Additional Information
You can use this demo page to test it out.