- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Feb 2025 18:29:05 +0000
- To: public-webrtc-logs@w3.org
I see no evidence that changing Chrome’s track order would cause breakage. Other browsers (Firefox and Safari) have always had different track orders with no ill effect. Any site _depending_ on a particular browser’s order is already non-interoperable, since the spec explicitly allows any order. Unifying behavior reduces confusion and helps developers. If there’s usage data showing a real dependency, that would be valuable, but absent that, fears of “breakage” seem unfounded. > - 99.8% of usage is going straight from GUM to addTrack IOW no issue for Chromium whose gUM order would remain unchanged: `[audio, video]`. > - 0.0063% of usage is stream.addTrack with a screensharing track and a microphone one. For extra fun 40% of those adds the mic to the screensharing stream, 60% the other way round. I bet this is where the new behavior would break. > And keep in mind that this affects SDP... There's no evidence websites rely on this order or that anything would break. There's evidence they don't (interoperable websites). If usage data for ordering assumptions exists, it would be good to see it. Absent that, we should not assume a hidden dependency that has somehow gone unreported despite existing browser differences. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2669447660 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 February 2025 18:29:05 UTC