- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Dec 2023 21:09:02 +0000
- To: public-webrtc-logs@w3.org
Developers need to be able to debug their users issues. Even if those issues extend beyond the JS application. For a developer of a VC application, the user agent, the operating system, even the hardware - everything is in scope.
> If the OS mutes, the user agent owns the problem of detecting that and conveying that as an "event" that happened.
As mentioned in my previous message, the user agent might not be able to understand why they are not receiving new frames. Issuing a `mute` event in such a case is both spec-compliant and **useful** (to developers).
> If the user agent has reason to believe lack of frames is instead due to an error, then ending the track may be more appropriate.
Why frames are not arriving would not always be known.
> If the user agent cannot tell whether the OS muted it or whether there was an error, that is its problem to solve.
Developers cannot afford to sit on their hands and pray that others would solve their problems. We live in a competitive world. He who solves their users problems promptly gains the prize of retaining his customers. Let's empower developers in their quest to serve our mutual users. ("Our mutual users" - shared by the browser and the Web app.)
> The spec already defines muted and ended as separate events for this reason.
You gave an example where you believe ending is better than muting. Even if I agreed, for the sake of argument, that this was correct - what about all other cases? Allow me to [quote](https://github.com/w3c/mediacapture-extensions/issues/39#issuecomment-1843866851) my colleague Guido: "We need to solve all use cases that arise in practice, not just the simplest one."
--
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1850891192 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 December 2023 21:09:04 UTC