This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21706 - Neuter the outputBuffer argument to AudioProcessingEvent after the event has been dispatched
Summary: Neuter the outputBuffer argument to AudioProcessingEvent after the event has ...
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-16 02:41 UTC by Ehsan Akhgari [:ehsan]
Modified: 2014-10-28 17:17 UTC (History)
0 users

See Also:


Attachments

Description Ehsan Akhgari [:ehsan] 2013-04-16 02:41:21 UTC
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.
Comment 1 Olivier Thereaux 2014-10-28 17:14:56 UTC
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 2 Olivier Thereaux 2014-10-28 17:17:55 UTC
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.