WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track being muted

[dontcallmedom]

Originally reported on W3C Bugzilla ISSUE-25513 Wed, 30 Apr 2014 07:12:28 GMT
Reported by Kiran
Assigned to

As discussed in Bug 25361 [1], WebRTC spec should explicitly specify all the muted events of a MediaStramTrack related to RTCPeerConnection

1. Tracks sourced from m-mline and marked as RecvOnly in SDP should be considered muted tracks.
2. Muted state resulted due to doohickey actions.

// May be some more other events related to PeerConnection.

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25361

[dontcallmedom]

Original comment by Harald Alvestrand on W3C Bugzilla. Fri, 31 Oct 2014 16:45:51 GMT

Editorial.

Note: Influenced by RTPSender/RTPReceiver.

[dontcallmedom]

Original comment by Harald Alvestrand on W3C Bugzilla. Wed, 05 Nov 2014 00:00:55 GMT

Note: The spec currently says that newly created MediaStreamTracks sourced from a PeerConnection have muted=true, but doesn't have any line in them saying that they set muted=false (and trigger onunmute) when media arrives.

This should be fixed in the same pass.

[stefhak]

Closing since #220 has been merged.