25513 2014-04-30 07:12:28 +0000 WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track being muted 2014-12-15 10:39:48 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified All All RESOLVED LATER P2 normal --- 1 kiran.guduru adam.bergkvist harald public-webrtc oldest_to_newest 104785 0 kiran.guduru 2014-04-30 07:12:28 +0000 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 114352 1 harald 2014-10-31 16:45:51 +0000 Editorial. Note: Influenced by RTPSender/RTPReceiver. 114537 2 harald 2014-11-05 00:00:55 +0000 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. 116339 3 dom 2014-12-15 10:39:48 +0000 WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues Please subscribe to the issues you want to keep watching.