- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Tue, 14 Apr 2026 18:58:24 +0000
- To: public-webrtc-logs@w3.org
For removal, some usual racy suspects from [count<2(status:pass) ?interop-2026](https://wpt.fyi/results/webrtc?label=master&product=firefox&product=chrome&product=safari&q=%20count%3C2%28status%3Apass%29%20%3Finterop-2026): - [RTCPeerConnection-remote-track-properties.https.html?interop-2026](https://wpt.fyi/results/webrtc/RTCPeerConnection-remote-track-properties.https.html%3Finterop-2026?label=master&product=firefox&product=chrome&product=safari&q=%20count%3C2%28status%3Apass%29%20%3Finterop-2026) - Remote audio track ID is different on different PCs - Remote video track ID is different on different PCs - [RTCRtpTransceiver-setCodecPreferences.html?interop-2026](https://wpt.fyi/results/webrtc/RTCRtpTransceiver-setCodecPreferences.html%3Finterop-2026?label=master&product=firefox&product=chrome&product=safari&q=%20count%3C2%28status%3Apass%29%20%3Finterop-2026) - setCodecPreferences should accept audio codecs regardless of mimeType case - setCodecPreferences should accept video codecs regardless of mimeType case But last we discussed these I think we said sometimes-pass is a pass, and that we should fix the tests instead. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4246393639 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 18:58:26 UTC