This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Assigned to me. (I should have been part of a previous edit I did.)
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.
Any update on where we are with this one ?
(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.