- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Dec 2023 21:20:35 +0000
- To: public-webrtc-logs@w3.org
> To make progress, I think we should leave the UA vs. OS muting discussion out of this particular issue. This can be resolved orthogonally to this discussion. > > The proposal is something like: > > 1. UAs refrain from firing mute events in malfunction cases. I don't see the justification for this. It draws a distinction between "malfunction" and "non-malfunction" that seems unwarranted and unenforceable (if an user unplugs the camera, it's a mute event; if the cat bites off the camera cable, it's a malfunction????) > 2. We design a shim based on MediaStreamTrack stats that emulates malfunctioning mute events. Since 1 is unjustified, 2 is unreasonable. Also, shims don't belong in the spec. If Firefox or Safari wish to emulate Chrome's behavior, they're free to incorporate a shim of that nature, but I don't see a point in changing Chrome's behavior. > 3. If MediaStreamTrack stats is not sufficient for 2, we augment the API surface (in MediaStreamTrack stats or elsewhere, new event e.g.). > 4. If the track is UA-muted, there is no stats, but there is no need to know whether malfunctioning or not. > > Other than requiring changes in UAs, I do not see any drawback. Am I missing something? Since I don't see the point of the change, I don't see any advantage in making it. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1865153933 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 21:20:37 UTC