- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Mon, 29 Sep 2025 16:31:33 +0000
- To: public-webrtc-logs@w3.org
> It seems strange that a receiver that isn't receiving any packets should remain unmuted indefinitely. Why is that strange? Mute is a forcible UA signal. Mute causes lack of frames. Lack of frames does not cause mute. A `mute` event says: _"stop looking for a cause of the lack of frames on this track. I am the cause"_. How is a receiver supposed to know that the lack of frames is intentional? That the sender used replaceTrack? The spec seems super clear here, and has been for a very long time. Remote tracks are deterministically muted when the receiver is the cause: to reflect negotiated direction changes on it, as only one part of [process remote tracks](https://w3c.github.io/webrtc-pc/#process-remote-tracks) algorithm. You might recall [this pivot](https://blog.mozilla.org/webrtc/the-evolution-of-webrtc): _"Remote tracks are now muted and temporarily removed from their stream(s), rather than ended, in response to direction changes (e.g. from removeTrack)"_. I'm not seeing any new information here. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3077#issuecomment-3347968614 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 September 2025 16:31:34 UTC