W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] Neuter the outputBuffer argument to AudioProcessingEvent after the event has been dispatched (#58)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:27:59 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/58@github.com>
> Originally reported on W3C Bugzilla [ISSUE-21706](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21706) Tue, 16 Apr 2013 02:41:21 GMT
> Reported by Ehsan Akhgari [:ehsan]
> Assigned to 

Similar to the neutering behavior for decodeAudioData's argument, we need to precisely define what happens when script attempts to access or modify AudioProcessingEvent.outputBuffer after the event has been dispatched.  The most efficient way to handle this would be to neuter the array buffers in outputBuffer so that the implementation can use the buffer without having to copy its data to an internal buffer in order to avoid being affected by any possible modifications coming from content after the event has been dispatched.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:29:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:10 UTC