- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Dec 2017 20:37:47 +0000
- To: public-webrtc-logs@w3.org
Is addTransceiver(kind or null) supposed to work the same as, or different from, this? ``` sender = pc1.addTrack(track); sender.replaceTrack(null); pc1.createOffer(), setLocalDescription and exchange offer/answer with pc2 ``` Because that would result in a sendrecv transceiver that is transmitting nothing (null track). Isn't addTransceiver() supposed to work the same such that you can replaceTrack() to immediately start sending without renegotiating? If it isn't sendrecv, wouldn't replaceTrack(track) on a transceiver created with addTransceiver() fail because renegotiation would be needed if the direction has to change? Or should replaceTrack() be updated to say to update the direction if it's not already sendrecv or sendonly? What happens with _"Determine if negotiation is needed to transmit withTrack in place of the sender's existing track."_ if direction is not sendrecv or sendonly? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-354354465 using your GitHub account
Received on Thursday, 28 December 2017 20:37:49 UTC