W3C home > Mailing lists > Public > public-media-capture@w3.org > May 2013

Re: [Bug 21618] New: MediaStreams with no tracks need to not be Ended

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 28 May 2013 11:30:57 +0200
Message-ID: <51A47951.9010708@alvestrand.no>
To: robert@ocallahan.org
CC: Adam Bergkvist <adam.bergkvist@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 05/28/2013 11:13 AM, Robert O'Callahan wrote:
> On Tue, May 28, 2013 at 9:04 PM, Harald Alvestrand 
> <harald@alvestrand.no <mailto:harald@alvestrand.no>> wrote:
>
>     So a stream will un-end itself if one adds a live track to it. I
>     can live with that.
>
> I'm not happy with that for the reasons in my message of April 9.
Rob, this message?

> We need to define an ended state for MediaStreams so that we know when 
> a media element with a MediaStream source should enter its ended 
> state. Furthermore, it should not suddenly leave its ended state 
> because a new track is added to the MediaStream ... that would be weird.
>
> Alternatively I suppose we could define that a media element with a 
> MediaStream source never ends, only pauses while all MediaStream 
> tracks are ended. However, it seems to me that it's useful to allow a 
> media element with a MediaStream source to end.
>
I thought we determined that it's possible for a MediaElement to exit 
its ended state if either the playing position was set or the direction 
changed (which can happen under JS control) - so it's consistent with 
MediaElement to have a transition from ended to not-ended because of 
things that JS does to the underlying object.
Received on Tuesday, 28 May 2013 09:31:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:17 UTC