[Bug 21777] Specify that audioprocess events should only be dispatched to ScriptProcessorNodes when they're connected to an output node

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21777

Alan deLespinasse <aldel@alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldel@alum.mit.edu

--- Comment #1 from Alan deLespinasse <aldel@alum.mit.edu> ---
Note that ScriptProcessorNode allows having zero outputs. It makes sense to
have a ScriptProcessorNode with one input and zero outputs, for example to do
some kind of analysis on the audio without producing a signal. In this case the
node can't be connected to an output, but obviously it should generate events.
(Though currently this doesn't seem to work, at least in the stable version of
Chrome.)

I'm not sure it would be wrong to generate events even if there are outputs
which aren't connected, considering that the event handler may have side
effects. But yes, the spec should specify this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 29 May 2013 20:45:30 UTC