- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Tue, 14 Apr 2026 19:45:44 +0000
- To: public-webrtc-logs@w3.org
I for one would like to point out that fixing `getStats succeeds on a closed peerconnection` (here)[https://wpt.fyi/results/webrtc/RTCPeerConnection-getStats.https.html%3Finterop-2026?label=experimental&label=master&aligned] was less than half an hour of effort (plus process) which leads to the question why despite addressing actual developers pain as evidenced by https://github.com/webrtcHacks/adapter/issues/1179 Mozilla has been unable to spend that time and why this was not in scope for interop 2024, 2025 etc. Thoughts @jan-ivar? > think we should keep https://wpt.fyi/results/webrtc/RTCPeerConnection-remote-track-properties.https.html%3Finterop-2026 @youennf can you please point me to spec language that justifies the tests "is different" and dropping available information from the msid unless there is a conflict? -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4246674395 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 April 2026 19:45:45 UTC