Re: [mediacapture-region] Is muting track the right call for empty cropped tracks (#9)

Mute has traditionally been "this track is not producing data, this was intentional, and we're not telling you why".

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 using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 8 March 2022 11:14:09 UTC