This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently, the spec says this: https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#JavaScriptAudioNode-section interface JavaScriptAudioNode : AudioNode { attribute EventListener onaudioprocess; readonly attribute long bufferSize; } An "onaudioprocess" property? This is not the right way to expose this. Instead, JavaScriptAudioNode should implement EventTarget, and thus get addEventListener, removeEventListener, etc. I'd prefer it if it removed the property, but I guess there is now some legacy content and there are some misguided developers who think that approach is acceptable. Then there should be a "audioprocess" event (or something like that).
I'd like to move away from EventListener here and change to a simpler Callback. It doesn't really make much sense to have multiple listeners since the processing should happen in a single place.
I guess this is a duplicate of Bug 17351 - right?
Well, Bug 17351 would be invalid if we go with a callback instead, which I agree we should do, for the reasons Chris mentions.
I believe that this is fixed; ScriptProcessorNode (the new name of JavaScriptAudioNode) no longer has anything to do with EventTarget (good!) The interfaces are now [1] interface ScriptProcessorNode : AudioNode { attribute EventListener onaudioprocess; readonly attribute long bufferSize; }; interface AudioNode { … }; [1] <https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#ScriptProcessorNode> There is a separate bug 20764 for using a proper callback instead of EventListener for onaudioprocess.
(In reply to comment #4) > I believe that this is fixed [...] > There is a separate bug 20764 for using a proper callback instead of > EventListener for onaudioprocess. Seeing no objection in almost a month, closing.