15593 2012-01-17 11:26:28 +0000 Update PeerConnection functionality associated to adding/removing MediaStreams 2012-05-21 12:30:40 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified PC Linux RESOLVED FIXED P2 normal --- 1 stefan.lk.hakansson adam.bergkvist adam.bergkvist fluffy fluffy harald public-webrtc oldest_to_newest 62805 0 stefan.lk.hakansson 2012-01-17 11:26:28 +0000 The current spec is not up to date in this respect. The MediaStream object at the receiving PeerConnection should be created immediately (with all tracks muted) as a result of signaling and not as a result of that RTP-packets are being received. 62889 1 adam.bergkvist 2012-01-19 08:53:11 +0000 Assigned to me. (I should have been part of a previous edit I did.) 66770 2 harald 2012-04-17 17:16:05 +0000 Note - I think removing MediaStreamTracks from a MediaStream should NOT change the index of other MediaStreamTracks on the MediaStream. Having them change creates a need for the other end of the PeerConnection to get the change signalled across to them, which may take time. 67882 3 fluffy 2012-05-18 14:59:39 +0000 Any update on where we are with this one ? 67960 4 adam.bergkvist 2012-05-21 12:30:40 +0000 (In reply to comment #3) > Any update on where we are with this one ? This has been fixed. https://github.com/fluffy/webrtc-w3c/commit/5777d833e43a3eebd2a909ba52423da664a9a10d https://github.com/fluffy/webrtc-w3c/commit/b1bdbbdb0a20ece3f37f295b2f6dc64477564a1a (In reply to comment #2) > Note - I think removing MediaStreamTracks from a MediaStream should NOT change > the index of other MediaStreamTracks on the MediaStream. > > Having them change creates a need for the other end of the PeerConnection to > get the change signalled across to them, which may take time. This should go into a bug of its own.