> Then again, this is one of those situations that a reasonable implementation should not care about. It would seem that Chrome, Chromium, or libWebRTC(not sure which at the moment) does care, based on the observed behaviour in Chrome. I'll try and see if I can reproduce this in other Chromium browsers and raise a bug. Given the observed behaviour in Chrome, the de-facto correct implementation becomes MUST at least until Chrome's behaviour is changed. -- GitHub Notification of comment by k0nserv Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2783#issuecomment-1294826750 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Friday, 28 October 2022 10:27:59 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC