- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Oct 2019 14:39:14 +0000
- To: public-webrtc-logs@w3.org
We all agree that the following sender should not be rolled back: ``` pc.setRemoteDescription(offer); sender = pc.addTrack(track); // sender from the transceiver created by the offer pc.setRemoteDescription(rollback); ``` But how about if we null the track? ``` pc.setRemoteDescription(offer); sender = pc.addTrack(track); // sender from the transceiver created by the offer sender.replaceTrack(null); pc.setRemoteDescription(rollback); ``` Probably we don't want to roll it back still? How about this one? ``` pc.setRemoteDescription(offer); pc.getTransceivers()[0].sender.replaceTrack(track); pc.setRemoteDescription(rollback); ``` It's not an "addTrack-transceiver", but we're trying to use it. What about this one? ``` pc.setRemoteDescription(offer); pc.getTransceivers()[0].direction = 'sendrecv'; pc.setRemoteDescription(rollback); ``` -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2324#issuecomment-539044177 using your GitHub account
Received on Monday, 7 October 2019 14:39:16 UTC