- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Feb 2025 21:40:07 +0000
- To: public-webrtc-logs@w3.org
It seems incumbent on those making unsubstantiated claims of "breakage" to provide evidence, and explain how breakage would manifest. I've provided plenty of evidence of absence: years of different browser orders without bug reports. > > 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. Which sites are those? > Let's unify then around Chrome's behavior. Unifying on Chrome’s historic ordering seems arbitrary. If we truly suspect real-world reliance, a usage counter could confirm that. Otherwise, there is no evidence of harm in converging on a single, simpler order that aligns [track set](https://w3c.github.io/mediacapture-main/#dfn-track-set) with https://infra.spec.whatwg.org/#sets > If we want to guarantee order for getTracks() we should also do it for getAudioTracks() and getVideoTracks(). Agreed. Those already appear expressed as the `track set` filtered on `kind`, so we'd just need to remove _"The conversion from the [track set](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-track-set) to the sequence is [User Agent](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-user-agent) defined and the order does not have to be stable between calls."_ -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2669821036 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 21:40:08 UTC