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 15593 - Update PeerConnection functionality associated to adding/removing MediaStreams
Summary: Update PeerConnection functionality associated to adding/removing MediaStreams
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-17 11:26 UTC by Stefan Hakansson LK
Modified: 2012-05-21 12:30 UTC (History)
5 users (show)

See Also:


Attachments

Description Stefan Hakansson LK 2012-01-17 11:26:28 UTC
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.
Comment 1 Adam Bergkvist 2012-01-19 08:53:11 UTC
Assigned to me. (I should have been part of a previous edit I did.)
Comment 2 Harald Alvestrand 2012-04-17 17:16:05 UTC
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.
Comment 3 Cullen Jennings 2012-05-18 14:59:39 UTC
Any update on where we are with this one ?
Comment 4 Adam Bergkvist 2012-05-21 12:30:40 UTC
(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.