- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Feb 2025 19:20:06 +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. > Absence of evidence is very different from evidence of absence. > Any site _depending_ on a particular browser’s order is already non-interoperable, since the spec explicitly allows any order. > We don't want to break those sites either. > 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. > Let's unify then around Chrome's behavior. If we want to guarantee order for getTracks() we should also do it for getAudioTracks() and getVideoTracks(). We can specify it as internally having two ordered sets, one for getAudioTracks() and one for getVideoTracks(). The order would be the order in which tracks are added to the corresponding set. getTracks() would return the concatenation of the audio set and the video set. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2669551344 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 19:20:07 UTC