- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 May 2023 18:46:25 +0000
- To: public-webrtc-logs@w3.org
In case your next question is who follows the spec on collectSenders and collectReceivers, this is (perhaps surprisingly) tested in https://wpt.fyi/results/webrtc/RTCDtlsTransport-state.html <img width="1411" alt="image" src="https://github.com/w3c/webrtc-pc/assets/3136226/df9f4439-f732-4897-8426-7c869939b011"> The red is browsers following the current spec, the green is Firefox not (the test is from Mozilla and seems backwards). * Given this, I think it makes sense to leave the sender in getSenders() on [[Stopping]] (current spec), ditto receivers, and fix the second test, but change the removeTrack spec language to abort explicitly if transceiver.[[Stopping]] --- <sub>*) The test tests both getReceivers() and getSenders() but it tests getReceivers() first which is why the error message says getReceivers(). Presumably they work the same for senders and receivers.</sub> -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2874#issuecomment-1570738544 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 May 2023 18:46:27 UTC