replaceTrack is sync before the transceiver is associated with a media section |
||
Issue descriptionThis means that before we do createOffer()/setLocalDescription(), performing RTCRtpSender.replaceTrack() is synchronous whereas after that it is asynchronous. The current implementation is always async, and as of writing this the WPT tests[1] test asynchronous behavior without doing the createOffer()/setLocalDescription() steps. See step 6 of replaceTrack in spec[2]. [1] third_party/WebKit/LayoutTests/external/wpt/webrtc/RTCPeerConnection-setRemoteDescription-replaceTrack.https.html [2] https://w3c.github.io/webrtc-pc/#dom-rtcrtpsender-replacetrack
,
Feb 12 2018
Thank you, that would be great!
,
Feb 12 2018
Though please see discussion in the issue.
,
Apr 24 2018
The spec has updated never to be sync, which means our implementation is correct in this regard. |
||
►
Sign in to add a comment |
||
Comment 1 by jbruar...@mozilla.com
, Feb 12 2018