Re: [webrtc-pc] WebRTC spec should explicitly specify all causes of a PeerConnection-sourced track being muted (#2915)

From yesterday's meeting I heard agreement that webrtc-pc should explicitly specify all causes of PeerConnection-sourced tracks being muted or unmuted, but some disagreement over what those causes are.

Since we have agreement we need to list causes here for event firing to be interoperable, the next steps I see are:
 1. Open separate issue/PR on mediacapture-main to clarify each source is responsible for specifying its mute behavior.
 2. Work out here the complete list of when `mute` and `unmute` events fire on remote tracks.


-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2915#issuecomment-1896675074 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 January 2024 20:56:58 UTC