- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Dec 2023 08:36:27 +0000
- To: public-webrtc-logs@w3.org
> This would solidify a model of muted being open ended and loosely defined. Even with the proposal here "mute" would still cover both OS-based and UA-based muting. Letting the Web app know which it is does not make it open ended or loosely defined. Carving out an "unspecified" for hardware, issues, or anything we might not be thinking of, does not solidify the model; later migration would be equally challenging then as it is now. > A dedicated event based API for each cause where mute might be useful would lead to better interop/convenience to web developers. I am not opposed to dedicated events, but they seem to be less elegant a solution, given the possibility of multiple concurrent mutes. Conversely, a single mute state with multiple reasons, allows observing the transition from empty set to non-empty set, which is great for apps that only care about that. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1864067469 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 December 2023 08:36:29 UTC