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

This is just buggy.  As discussed in some thread, a MediaStream state
- if it exists at all - should just be a rollup of MediaStreamTrack
states.  That would make c) invalid, which is the real problem here.

Then the state of a MediaStream with no tracks becomes largely
acedemic.  Maybe it is ended because it has no un-ended tracks.  Maybe
it is un-ended because all of its tracks are not ended.

On 8 April 2013 05:19,  <bugzilla@jessica.w3.org> wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21618
>
>             Bug ID: 21618
>            Summary: MediaStreams with no tracks need to not be Ended
>     Classification: Unclassified
>            Product: WebRTC Working Group
>            Version: unspecified
>           Hardware: PC
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: Media Capture and Streams
>           Assignee: public-media-capture@w3.org
>           Reporter: harald@alvestrand.no
>                 CC: public-media-capture@w3.org
>
> According to the current specs:
> a) it is possible to create a MediaStream that has no tracks.
> b) if all the tracks in a MediaStream are ended, the state of the MediaStream
> is ended
> c) You can't add tracks to a MediaStream that's ended.
>
> b) is ambiguous for the case where there are no tracks: Is it ended or not?
> If it is ended, creating a MediaStream with no tracks becomes useless, and
> removing all tracks from a MediaStream will end it - rendering it useless.
>
> If it is not ended, the MediaStream is useful - but it also becomes possible to
> "un-end" a MediaStream by removing all its tracks.
>
> A decision is sought.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.
>

Received on Monday, 8 April 2013 22:43:58 UTC