- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jan 2024 09:37:49 +0000
- To: public-webrtc-logs@w3.org
> The present language seems to be intended to not fire negotiationneeded when you change from sendrecv to recvonly or sendonly. I'm not sure that's wise, but that's how I interpret the language.
Hrm... could that lead to removeTrack on a sendrecv transceiver without a track not firing which is unexpected:
https://jsfiddle.net/fippo/vd3mgp5k/1/
With `addTransceiver('audio')` it does not fire, with `addTransceiver(audioTrack)` it fires.
Now that seems ok since no track is removed in the first case but it means that removeTrack behaves quite differently depending on the history of the transceiver.
Footgun alert...
--
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2919#issuecomment-1875081357 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 January 2024 09:37:51 UTC