This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21967 - Clarify enabled state for new MediaStreamTrack's
Summary: Clarify enabled state for new MediaStreamTrack's
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
: 22212 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-08 13:57 UTC by Stefan Hakansson LK
Modified: 2013-08-27 08:53 UTC (History)
3 users (show)

See Also:

Attachments

Description Stefan Hakansson LK 2013-05-08 13:57:21 UTC 
There are four ways currently to create new tracks:

* existing_track.clone
* existing_mediastream.clone (which reuses existing_track.clone)
* constructors for AudioStreamTrack and VideoStreamTrack
* getUserMedia (returning a MediaStream with MediaStreamTracks)

However, as far as I can tell there is no text saying what the "enabled" state is for the new track. This should be clarified (and probably be "enabled" in all those cases).
Comment 1 Dominique Hazael-Massieux 2013-05-30 21:04:36 UTC 
*** Bug 22212 has been marked as a duplicate of this bug. ***
Comment 2 Harald Alvestrand 2013-06-20 11:33:24 UTC 
Discussion on the list June 18 to June 19, 2013.
Conclusion:

- All newly created tracks should have "enabled=true"
- Tracks created from another track, either by MediaStream.clone() or by MediaStreamTrack.clone(), should get the same state of "enabled" as the track they are cloned from.

This seems to be uncontroversial. Assigning to Adam for editing.
Comment 3 Harald Alvestrand 2013-08-27 08:53:30 UTC 
Resolved in 20130824 version of MediaCapture.