- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 13:58:35 +0000
- To: public-webrtc-logs@w3.org
We define APIs so that developers can satisfy user needs for applications running on a specific UA. The UA has no needs; it exists to satisfy the user - in the case of JS apps, to let the app developers satisfy the users. The UA and the OS are not friends. And the user has a direct relationship to both. When an OS-level mute is applied, and can only be rectified using the user's relationship with the OS, the user *needs to know that it has to act in relation to the OS*. If the OS offers API to the UA so that the UA can let the app developer satisfy the user's need (in this case: to unmute), the user's needs will be simpler to satisfy. The difference between muted and ended in our specs is that one is reversible, the other isn't. So anything that is not based on a clear signal that the source is gone and won't come back should be "muted", not "ended". "Reason to believe" sounds like "probable cause", not "clear signal". -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1853969778 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 13:58:37 UTC