New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 627261 link

Starred by 19 users
Status: Duplicate
Merged: issue 700916
Owner:
█ deadbeef@chromium.org
Last visit > 30 days ago
Closed: Mar 2017
Cc:
█ emadomara@chromium.org
webrtc-network-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature

Blocking:
issue webrtc:2131
issue 642712
issue 651800



Sign in to add a comment

PeerConnection.getSenders and getReceivers

Project Member Reported by deadbeef@chromium.org, Jul 11 2016 
Implement getSenders and getReceivers as specified: https://www.w3.org/TR/webrtc/#rtcpeerconnection-interface-extensions

Sender and receivers should expose, at a minimum, the `track` attribute, with senders also supporting the `replaceTrack` method.

Chrome tracking feature: https://www.chromestatus.com/feature/5347809238712320

Comment 1 by weili1...@gmail.com, Jul 11 2016 

I would appreciate notice on Chrome development of RTCRtpSender.replaceTrack feature.

Thanks.

-wei,

Comment 2 by deadbeef@chromium.org, Nov 11 2016

Blocking: 651800

Comment 3 by deadbeef@webrtc.org, Nov 12 2016

Blocking: webrtc:2131

Comment 4 by deadbeef@chromium.org, Nov 12 2016

Components: -Blink>WebRTC Blink>WebRTC>Network

Comment 5 by deadbeef@chromium.org, Nov 12 2016

Blocking: 642712

Comment 6 by hbos@chromium.org, Mar 14 2017

Mergedinto: 700916
Status: Duplicate (was: Assigned)
RTCRtpSender: https://crbug.com/700916
RTCRtpReceiver: https://crbug.com/701330
►

Sign in to add a comment