W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 20039] New: The callbacks of the decodeAudioData API are underspecified

From: <bugzilla@jessica.w3.org>
Date: Thu, 22 Nov 2012 00:17:58 +0000
To: public-audio@w3.org
Message-ID: <bug-20039-5429@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20039

            Bug ID: 20039
           Summary: The callbacks of the decodeAudioData API are
                    underspecified
    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

Here is a list of problems that come to my mind right now.

1. It's not clear whether the callbacks have to be asynchronous or not.  For
example, if for some reason the implementation decides that it's unable to
decode the audio right away, should it just call the failure callback directly,
or call it the next time that the execution hits the event loop.

2. It's not clear what the AudioBuffer callback passed to the failure callback
should contain.  For example, if the audio's type cannot be sniffed, what
should be passed to the failure callback?  What if the source buffer doesn't
contain valid samples and the decoding operation fails half-way?

3. "The ArrayBuffer can, for example, be loaded from an XMLHttpRequest with the
new responseType and response attributes." should probably converted to "The
ArrayBuffer can, for example, be loaded from an XMLHttpRequest's response
attribute after setting the new responseType to "arraybuffer"."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 22 November 2012 00:17:59 UTC

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