- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 16:15:34 +0000
- To: public-webrtc-logs@w3.org
Let's not broaden discussion to include unrelated issues. Evidence of B is not evidence of A. > websites may > 1/ not care about the order or do not rely on getTracks() order. There is no problem in having different orders so no action needed. That's a false choice. The status quo relies on interop-hygiene among web developers, which can be effective AND not great at the same time. It's our job to ensure long-term interop. So it seems a totally reasonable position for me to suggest there's no breakage today given the evidence, AND saying this may not hold in the future as more advanced multi-track uses appear, or say interest in interop among WebRTC-related web developers dips. > "Needlessly confusing web developers" is not a good thing. The current spec relies on interop hygiene among web developers. We should thank them for staying interoperable so far, and fix the spec to relieve them of carrying this interop burden, which they should never have had (we didn't know better back then). Hopefully, we can all agree that standardizing one behavior would be beneficial, and that we're down to picking what that behavior should be. Any evidence of track order dependency would be helpful to this WG in making the decision of what behavior to pick. > A "theoretical purity" argument carries very little weight. Track order is directly observable, and hence not "theoretical". I think you mean logically consistent observable behavior. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2685540158 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 February 2025 16:15:36 UTC