- From: Coread via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Mar 2023 10:58:29 +0000
- To: public-webrtc-logs@w3.org
> Options like `selfBrowserSurface`, `systemAudio`, etc., affect the capture-session, not the track. One way to think of it is - would it ever make sense to `applyConstraints({...selfBrowserSurface: "exclude", ...})`. It wouldn't, so these aren't MediaStreamTrack constraints.
Thanks for the explanation of the distinction between constraints and options.
I think displaySurface is an odd case. Because it merely suggests which surface is to be displayed, it does not have the effect of a constraint. However it is a property of the resulting media track.
To me it feels slightly strange to have displaySurface as a constraint, but then have something that controls which display surface e.g. the proposed monitorTypeSurfaces be an option. What do you think?
--
GitHub Notification of comment by Coread
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/260#issuecomment-1480982342 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 March 2023 10:58:31 UTC