- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Mar 2022 11:14:07 +0000
- To: public-webrtc-logs@w3.org
Mute has traditionally been "this track is not producing data, this was intentional, and we're not telling you why". https://w3c.github.io/mediacapture-main/getusermedia.html#track-muted Do we have an operational need for the application to know why the track is muted, that can't be solved by the capturer inspecting the situation in other ways, for instance by inspecting the HTMLElement it did produceCropTarget() on? If adding MuteCause, I'd add this to CropTarget, not to MediaStreamTrack. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/9#issuecomment-1061667555 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 March 2022 11:14:09 UTC