Re: The issue of ScriptProcessorNode not being an EventTarget

On Mon, Mar 4, 2013 at 3:01 PM, Ehsan Akhgari <ehsan@mozilla.com> wrote:

> This issue is still pending but we need to move forward with _a_ decision
> on the Gecko side of things, so I'm just going to assume that the spec is
> going to get updated to make AudioNode an EventTarget and make
> onaudioprocess an EventHandler.
>
> Cheers,
>
> --
> Ehsan
> <http://ehsanakhgari.org/>
>

Hi Ehsan, I had hoped we could make it be a simple Callback, but this
doesn't seem to really affect what the JS code using the API would look
like, so I'm not that hung up on it.  I certainly don't want to block any
progress you're making with the OfflineAudioContext.

Chris


>
>
> On Thu, Jan 24, 2013 at 6:49 PM, Ehsan Akhgari <ehsan@mozilla.com> wrote:
>
>> Olli filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=20764 a few
>> minutes ago.  This is a bug that I hit when I was trying to implement
>> ScriptProcessorNode.  Basically, as things stand, ScriptProcessorNode is
>> not implementable in Gecko without the sort of hacks which WebKit seems to
>> be going through, and we would really like to avoid that.
>>
>> It look like the best way to deal with this is to make AudioNode inherit
>> from EventTarget, and make onaudioprocess an EventHandler.
>>
>> This is currently very high priority for the Gecko implementation since
>> we are on the verge of landing initial audio playback support, and we need
>> to implement ScriptProcessorNode as a way to test the ongoing work on the
>> audio playback support.
>>
>> Chris, I'd appreciate if you could please take a look into this and
>> address this issue at the spec level.  It's sort of a big change, so I
>> don't want to just assume things and proceed on the implementation side.
>>
>> Thanks!
>> --
>> Ehsan
>> <http://ehsanakhgari.org/>
>>
>
>