W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: onEnded and connections

From: Chris Wilson <cwilso@google.com>
Date: Wed, 4 Sep 2013 16:02:59 -0700
Message-ID: <CAJK2wqUKc-vvRoaOxRERS8Fq3OQR4PF4V6WQ3dt7sUA6ud-a8A@mail.gmail.com>
To: Ehsan Akhgari <ehsan.akhgari@gmail.com>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, "public-audio@w3.org" <public-audio@w3.org>
On Wed, Sep 4, 2013 at 3:27 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com>wrote:

> On Wed, Sep 4, 2013 at 6:03 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
>
>>
>> On Thu, Sep 5, 2013 at 9:44 AM, Chris Wilson <cwilso@google.com> wrote:
>>
>>> Say you have a source node and set up an event handler for onended.
>>>  Does the event handler fire if the buffer is not actually connected to
>>> anything?
>>>
>> If the source is never connected to anything and it is GCed, onended
>>> should not be called, right?
>>>
>>
>> Whether ended is fired must definitely not depend on when GC happens. GC
>> timing causing observable behavior changes is anathema.
>>
>> The answer to your first question is less clear. The question itself is
>> also ambiguous: do you mean "not directly connected to an output" or "not
>> indirectly connected to a DestinationNode or MediaStreamAudioSourceNode"?
>> You'd also have to resolve *when* exactly the graph connectivity check is
>> performed. In any case, the simplest API is to fire the event no matter
>> what, and that's what Gecko does.
>>
>
> Yes, that was our intention when we added this event to the spec.
>

That is certainly ambiguous in the spec, and Chris' view of connections was
pretty different (than mine, even).

-Chris
Received on Wednesday, 4 September 2013 23:03:26 UTC

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