W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2013

[Bug 21706] New: Neuter the outputBuffer argument to AudioProcessingEvent after the event has been dispatched

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Apr 2013 02:41:21 +0000
To: public-audio@w3.org
Message-ID: <bug-21706-5429@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21706

            Bug ID: 21706
           Summary: Neuter the outputBuffer argument to
                    AudioProcessingEvent after the event has been
                    dispatched
    Classification: Unclassified
           Product: AudioWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Audio API
          Assignee: crogers@google.com
          Reporter: ehsan@mozilla.com
        QA Contact: public-audio@w3.org

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 April 2013 02:41:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:18 UTC