The complete
event of the OfflineAudioContext
interface is fired when the rendering of an offline audio context is complete.
Bubbles | No |
---|---|
Cancelable | No |
Default action | None |
Interface | OfflineAudioCompletionEvent |
Event handler property | OfflineAudioContext.oncomplete |
Examples
When processing is complete, you might want to use the oncomplete
handler the prompt the user that the audio can now be played, and enable the play button:
let
offlineAudioCtx= new OfflineAudioContext();
offlineAudioCtx.addEventListener('complete', () => { console.log('Offline audio processing now complete'); showModalDialog('Song processed and ready to play'); playBtn.disabled = false; })
You can also set up the event handler using the OfflineAudioContext.oncomplete
property:
let
offlineAudioCtx= new OfflineAudioContext();
offlineAudioCtx.oncomplete = function() { console.log('Offline audio processing now complete'); showModalDialog('Song processed and ready to play'); playBtn.disabled = false; }
Specifications
Specification | Status | Comment |
---|---|---|
Web Audio API The definition of 'OfflineAudioCompletionEvent' in that specification. |
Working Draft |
Browser compatibility
The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
complete event | Chrome Full support 14 | Edge Full support 12 | Firefox Full support 25 | IE No support No | Opera Full support 15 | Safari Full support 6 | WebView Android Full support Yes | Chrome Android Full support 18 | Firefox Android Full support 26 | Opera Android Full support 14 | Safari iOS ? | Samsung Internet Android Full support 1.0 |
Legend
- Full support
- Full support
- No support
- No support
- Compatibility unknown
- Compatibility unknown