Issue metadata
Sign in to add a comment
|
PeerConnection.addTrack should be implemented |
||||||||||||||||||||||||
Issue descriptionPer https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack the right method to add an outgoing track to a RTCPeerConnection is "addTrack". The only implemented method at the moment is "addStream".
,
Oct 26 2016
,
Nov 10 2016
This is already implemented in the native library: https://cs.chromium.org/chromium/src/third_party/webrtc/api/peerconnectioninterface.h?sq=package:chromium&rcl=1478794702&l=391 It just needs to be wired up to Chrome/Blink. Eventually we should then deprecate the behavior where if you call "addStream", then later add a track to that stream, it will end up added to the PeerConnection. addStream should end up as a polyfill that just calls addTrack for each track in the stream.
,
Nov 12 2016
Oh, but I forgot, addTrack returns an RTCRtpSender. So this is blocked on implementing RtpSenders.
,
Mar 14 2017
,
Mar 29 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Aug 31 2016