Re: [webrtc-pc] addTransceiver woes

If a transceiver that has already been negotiated is reused for addTrack(), and addTrack() essentially just does replaceTrack(), I would assume renegotiation is not needed and the spec saying it is would be a spec bug.
But if addTrack() is essentially just doing replaceTrack(), why can addTrack() be sync when replaceTrack() is said to be async?

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-354421240 using your GitHub account

Received on Friday, 29 December 2017 09:26:58 UTC