- From: Michał Śledź via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jan 2024 10:22:26 +0000
- To: public-webrtc-logs@w3.org
The same will happen if we call replaceTrack(null) before calling removeTrack > 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. I am not sure. To have sendrecv in local answer the other side had to offer sendrecv so after changing to sendonly or recvonly on the answerer side, the intersection will always differ. Take a look here, pc2 changes direction from sendrecv to recvonly and negotiationneeded is fired https://jsfiddle.net/pxrzh086/1/ -- GitHub Notification of comment by mickel8 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2919#issuecomment-1875137865 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 10:22:28 UTC