This allows you to seamlessly change which track is being sent without having to renegotiate at the expense of another offer/answer cycle. For example, you might want to switch which video to send or to temporarily not send video, without any disruption in audio or at the cost of an RTT delay. It can also be used to control whether or not to send with replaceTrack(null).

Specification

Editor's draft

Status in Chromium

Blink>JavaScript>API


Enabled by default (tracking bug) in:

  • Chrome for desktop release 65
  • Chrome for Android release 65
  • Android WebView release 65

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Shipped/Shipping
  • No signal
  • No signal
  • No signals

Owner

Search tags

WebRTC RTCPeerConnection RTCRtpSender replaceTrack MediaStreamTrack,

Last updated on 2020-11-09