> So if you do setRemoteDescription() followed by addTrack() the resulting behavior observed would always be as if you invoked addTrack() first and setRemoteDescription() second? Yes. > Can you clarify, would this be any different from if you had awaited setRemoteDescription() first and performed addTrack() second? I think the net result is the same, but I'd appreciate a second pair of eyes. The assumption here is that the incoming SRD creates a transceiver that we want to associate with. In the latter case, we'd be in `"have-remote-offer"` so this transceiver's currentDirection would still be `null` and satisfy the absorption criteria in [addTrack](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack). -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2504#issuecomment-606860571 using your GitHub accountReceived on Tuesday, 31 March 2020 20:36:26 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:50 UTC