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

Re: onEnded and connections

From: Joseph Berkovitz <joe@noteflight.com>
Date: Wed, 4 Sep 2013 17:50:49 -0400
Cc: "public-audio@w3.org" <public-audio@w3.org>
Message-Id: <97EED1C8-9390-40FC-9A83-59B930D0F5AA@noteflight.com>
To: Chris Wilson <cwilso@google.com>
From my point of view, onended only makes sense if it reflects the cessation of actual playback. These other conditions are not the "end" of anything, so +1 on both of your hypotheses. And of course, either way is a spec change.

On Sep 4, 2013, at 5:44 PM, Chris Wilson <cwilso@google.com> wrote:

> Engineer on our team asked a question that I think needs a spec change either way.  
> --
> 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?
> 
> Let's say you do something like start(3600) and then disconnect the the source node from the graph before the source starts playing.  onended should not be called, right?
> 
> -C

.            .       .    .  . ...Joe

Joe Berkovitz
President

Noteflight LLC
Boston, Mass.
phone: +1 978 314 6271
www.noteflight.com
"Your music, everywhere"


Received on Wednesday, 4 September 2013 21:51:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:23 UTC