[mediacapture-main] Clarify each source is responsible for specifying mute/unmute behavior (#984)

jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-main:

== Clarify each source is responsible for specifying mute/unmute behavior ==
From https://github.com/w3c/webrtc-pc/issues/2915#issuecomment-1896675074:
> 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.

Different sources (e.g. RTCPeerConnections or canvas) have different mute/unmute needs.  Other specs need a clean slate to specify only what "MUST/MAY" happen (not what "MUST NOT" happen) which is generally considered a more extensible way of writing specs. Spelling this out should help readers, implementers, and interoperability.

Strangely, [17. Extensibility](https://w3c.github.io/mediacapture-main/getusermedia.html#extensibility) has no section for _"Defining new source of MediaStreams and MediaStreamTracks"_. That's probably where this should go.

Mediacapture-main could be also be clearer about when it's talking about microphone and camera sources, since these have unique mute/unmute needs tied to privacy features of the microphone and camera in the OS or UA to protect the end-user's privacy.

Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/984 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 21:39:58 UTC