- From: youennf via GitHub <noreply@w3.org>
- Date: Thu, 09 Apr 2026 12:08:09 +0000
- To: public-webrtc-logs@w3.org
Some tests to be looked at: - https://wpt.fyi/results/webrtc/back-forward-cache-with-open-webrtc-connection.https.window.html?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2026-webrtc should probably be removed. There is no spec stating whether RTCPeerConnection should prevent entering page cache or not. Safari is supporting it, Chrome and Firefox are not. Ultimately, supporting page cache should prevail or the spec should disallow page cache. - https://wpt.fyi/results/webrtc/protocol/h264-profile-levels.https.html%3Finterop-2026?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2026-webrtc. It might be good to have @alvestrand input. My interpretation is that Safari is passing the test as there is bandwidth adaptation done by reducing the resolution. Using `maintain-resolution` might provide better results. I would tend to move this test out of interop 2026. I think @jan-ivar has a list of other tests that should be added/removed. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4214081142 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 April 2026 12:08:09 UTC