- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Fri, 15 May 2026 05:51:07 +0000
- To: public-webrtc-logs@w3.org
> Actually, this particular difference of behavior between UAs created a real interop issue. You are refering to [this quirk](https://github.com/WebKit/WebKit/commit/97ebd29ad20339f333d3bf60bd40c889e381a586). This should no longer be necessary, please verify. I also landed a [one-line fix in Chromium](https://chromiumdash.appspot.com/commit/bf63624ab8cb35a1398adf5115b33216a52cdd4a) which turned into ~10 LoC because killswitches, 🤞 it sticks in M150. This is another sad example of the problem the WebRTC Working Group has in my opinion: * [chromium issue filed in 2020](https://issues.chromium.org/issues/40684245), nobody had time to fix it. I had not even seen it. * the [spec is changed for aesthetics](https://github.com/w3c/webrtc-pc/pull/2510). It could have been changed to just set the irrelevant label to the track id. * Some app did it wrong, Trivial fix, they just need to be aware. And find time. * Safari adds a "quirk". Safari now works in that app, In-app E2E test coverage is probably missing. * For some reason this lands here as a "interop problem". If Chromium had fixed it surely the offending app would have been *forced* to fix this! Good thing that not only actually fixing problems got cheaper (four 🍻 so far), generating images for every situation did too! <img width="200" height="269" alt="Mommy, why does everyone only invite Chrome?" src="https://github.com/user-attachments/assets/a6894abf-de6a-428e-a975-d0232f216035" /> > It's near the bottom of that list. Look for the green dot in a sea of red. The world is more than WPT and fiddles. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4457249818 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 May 2026 05:51:08 UTC