- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Thu, 30 Apr 2026 00:57:01 +0000
- To: public-webrtc-logs@w3.org
> But yes, in that light pushing Chrome to fix the remote track label seems like an "appropriate goal" to take on. We followed public and neutral _"[pass in 2/3 engines](https://github.com/web-platform-tests/interop/issues/1101#issuecomment-3626318031)"_ baseline criteria for subtest inclusion in Interop 2026 (with chairs treating sometimes-pass as pass to meet the 2/3, excluding false positives). I think you'll find this explains all subtests nominated for inclusion, so I wouldn't read anything more into it than that. > ... [support for two byte RTP header extensions (RFC 5285, July 2008)](https://wpt.fyi/results/webrtc/protocol/rtp-headerextensions.html?label=experimental&label=master&aligned) somehow fell through the cracks despite work being done [here](https://bugzilla.mozilla.org/show_bug.cgi?id=2014357)? Those are [part of interop 2026](https://wpt.fyi/results/webrtc/protocol/rtp-headerextensions.html?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2026-webrtc) as is anything findable from https://wpt.fyi/interop-2026. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4348695016 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 April 2026 00:57:02 UTC