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 25513 - WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track being muted
Summary: WebRTC spec should explicitly specify all causes of a PeerConnection-sourced ...
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-30 07:12 UTC by Kiran
Modified: 2014-12-15 10:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Kiran 2014-04-30 07:12:28 UTC 
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
Comment 1 Harald Alvestrand 2014-10-31 16:45:51 UTC 
Editorial.

Note: Influenced by RTPSender/RTPReceiver.
Comment 2 Harald Alvestrand 2014-11-05 00:00:55 UTC 
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.
Comment 3 Dominique Hazael-Massieux 2014-12-15 10:39:48 UTC 
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.