- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Dec 2023 22:58:54 +0000
- To: public-webrtc-logs@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc: == WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track being muted == In https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1853733588 @guidou wrote: > > 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]. [Crbug 941740](https://crbug.com/941740) has been open for almost 5 years without mention of this, and I'd argue [ยง 9.3 MediaStreamTrack](https://w3c.github.io/webrtc-pc/#mediastreamtrack-network-use) _does "state a new definition of muted specific for WebRTC tracks"_: <img width="848" alt="image" src="https://github.com/w3c/webrtc-pc/assets/3136226/fb6baa51-0093-41b7-a5e5-f2ff6ebfd7f6"> I would argue this describes _all_ causes of mute for remote tracks, based on https://github.com/w3c/webrtc-pc/issues/139. But @guidou is right that it: 1. it does not say anywhere that this overrides the model defined in the original MediaStreamTrack specification. 2. does not list the muted/unmuted events in its Event Summary section But this seems editorial as evidenced by #139. Both specs needs to clarify that while this spec follows the _model_ in mediacapture-main, each source is responsible for specifying its own mute/unmute behavior, if any. We did this for constraints, and it only makes sense to do the same here. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2915 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 22:58:56 UTC