WebRTC Interop

[youennf]

Description

WebRTC is, by nature, a complex technology. Complexity can lead to compatibility and reliability issues.
It would thus be valuable to raise the level of WebRTC interoperability observed in WPT webrtc tests.

The current pass rate in the WPT webrtc tests folder is slightly above 80% (from 81 to 87%) and could be increased further.
429 tests out of 2150 are uniquely failing in one of Chrome, Firefox or Safari.

Specification

https://w3c.github.io/webrtc-pc/

web-feature

No response

Test Links

https://wpt.fyi/results/webrtc, except https://wpt.fyi/results/webrtc/legacy

Additional Signals

No response

[github-actions]

This comment was automatically generated based on the information you provided. Please don't edit it.

Below is additional information about the web feature (from the web-features project) which is referenced in your proposal.
If this doesn't accurately correspond to your proposal, please update your initial comment to include web-features: <feature-id>.
To find feature IDs, use the web-features explorer.

Feature WebRTC

• ID: webrtc
• Name: WebRTC
• Description: The WebRTC API establishes real-time communication channels directly between browsers. It is commonly used in video conferencing applications.
• Baseline status: Widely Available
• Docs: WebRTC API
• More information: See the web-features explorer

[gsnedders]

except https://wpt.fyi/results/webrtc/legacy

With regards to the non-optional tests in this directory: web-platform-tests/wpt#49559 removes a test which contradicts another WebRTC test and has no basis in the spec or WG consensus, and web-platform-tests/wpt#49560 moves another test out of that directory because it isn't in the same optional behaviour category as the rest. The rest of the tests are marked as optional.

[jgraham]

"All the WebRTC tests" might be quite a large scope. One way to cut this down would be to concentrate on the tests which currently pass in 2/3 engines: https://wpt.fyi/results/webrtc?label=master&product=firefox&product=chrome&product=safari&q=%21tentative%20count%3D2%28status%3Apass%29%20%21legacy%20%21anyCodec This would mean that the focus area got almost-working features up to full interoperability.

[youennf]

This was discussed at TPAC WebRTC WG meeting. Ideally, the WebRTC WG members would be responsible to triage the webrtc tests in Q1 2026, and browser implementors would work on the tests selected during this triage period.
As you mentioned, the baseline would be single-browser failures but other tests could be included (for instance web-platform-tests/wpt#55873).

[wpt-interop]

Thank you for proposing WebRTC Interop for Interop 2026.

We are pleased to let you know that it has been accepted as part of the WebRTC focus area.

You’ll be able to track progress on this topic throughout the year via the Interop 2026 dashboard.

Posted on behalf of the Interop team.