- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Dec 2023 23:35:35 +0000
- To: public-webrtc-logs@w3.org
> > For example: [crbug 941740](https://crbug.com/941740) implements mute on remote tracks reactively based on (lack of) input, violating the WebRTC spec and causing web compat issues. > > In this case, Chromium just is applying the model defined in the main spec to remote tracks. The WebRTC spec indicates some cases in which the muted attribute should be set/unset, but AFAICT it does not say anywhere that this overrides the model defined in the original MediaStreamTrack specification. It also does not state a new definition of muted specific for WebRTC tracks and does not even list the muted/unmuted events in its [Event Summary section]. This seems wrong. I've filed https://github.com/w3c/webrtc-pc/issues/2915 on this. Let's discuss that there. I think I see now how we came to have this vague language. MediaCapture-main is trying to establish both a _model_ for all sources, while simultaneously specifying camera and microphone sources explicitly. I think it needs to do a better job separating when it's doing one or the other. At its core, I think most people consider muting to be a conscious action based on intent. A reason, not a reaction. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1861857452 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 December 2023 23:35:37 UTC