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

Re: Audio-ISSUE-60 (addEventListener): AudioNode.addEventListener not defiend [Web Audio API]

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Tue, 15 May 2012 22:58:22 +0300
Message-ID: <4FB2B55E.8040705@helsinki.fi>
To: Audio Working Group <public-audio@w3.org>
On 05/15/2012 06:59 PM, Audio Working Group Issue Tracker wrote:
> Audio-ISSUE-60 (addEventListener): AudioNode.addEventListener not defiend [Web Audio API]
>
> http://www.w3.org/2011/audio/track/issues/60
>
> Raised by: Philip J├Ągenstedt
> On product: Web Audio API
>
> It's not clear if addEventListener is supposed to be supported or not. If it should be supported, the correct way is probably to inherit EventTarget from DOM4: http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#interface-eventtarget
>
>
>

Well, at least JavaScriptAudioNode must be EventTarget.
Otherwise you can't dispatch audioprocess event to it.
And once you can dispatch the event, AudioProcessingEvent.node is the same
thing as .target. So, .node could be removed.

Though, per the draft only onaudioprocess event handler is called with the event as
parameter. That is unique way to use events in the web platform.
Received on Tuesday, 15 May 2012 19:58:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 May 2012 19:58:52 GMT