- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Thu, 02 Oct 2025 21:57:05 +0000
- To: public-webrtc-logs@w3.org
> 2 RTCP reporting intervals is, what, maybe 10 seconds? 20 seconds tops? > > This is demonstrably not implemented and would make `replaceTrack(null)` a complete foot-gun. The timeouts—15s for audio and 3s for video ([5 and 1](https://searchfox.org/firefox-main/search?q=rtcp_report_interval_ms&redirect=false) x [3](https://searchfox.org/firefox-main/rev/6f3037f71baa242161ed343cdccb12c1b8e50227/third_party/libwebrtc/modules/rtp_rtcp/source/rtcp_receiver.cc#81,96,98,100))—are _RTCP_ timeouts, not RTP timeouts, so `replaceTrack(null)` doesn't cause timeout. It _is_ implemented in Firefox behind the `media.peerconnection.mute_on_bye_or_timeout` pref in about:config: https://jsfiddle.net/jib1/p3c1ovn8/ shows Firefox (w/ or wo/pref) does _not_ mute the remote track after clicking the `replace w/null` button even after several minutes (Chrome does due to [crbug 941740](https://crbug.com/941740); Safari doesn't) -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3077#issuecomment-3363353767 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 October 2025 21:57:06 UTC