Re: [mediacapture-main] Should we revisit and document getUserMedia() track order? (#1028)

> An outcome completely consistent with the evidence presented so far is that the browser that changes its behavior starts to receive bug reports, and the browsers that keep their behavior continue to receive no bug reports.
Keeping the status quo where no one changes its behavior is likely to continue to result in no bugs.

That argument ignores the actual evidence that browsers have already changed this behavior (or never matched Chrome’s) with no bug reports. If track ordering were a real point of failure, we’d see it in Safari or Firefox, which have behaved differently for years. Suggesting a new change might produce bug reports assumes a risk we’ve effectively tested in the real world already—and we’ve seen no problems.

The status quo proves we can safely change behavior here to align with Web Platform Infra. Why do so? Because future uses of WebRTC might be more plentiful and involve more tracks than today's use. Just because it's no problem today doesn't mean it won't be tomorrow. 

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1028#issuecomment-2682820674 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 25 February 2025 17:40:03 UTC