- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Sep 2021 13:58:17 +0000
- To: public-webrtc-logs@w3.org
> If the [displaySurface](https://w3c.github.io/mediacapture-screen-share/#dfn-displaysurface) constraint wasn't already defined then perhaps a different API might have value
There are a few reasons:
- The spec is talking about displaySurface as a setting and as a capability, not as a constraint, contrary to suppressLocalAudioPlayback say. Are browsers rejecting {displaySurface: { exact :...}}
- displaySurface is not currently supported in implementations as a constraining value. The way we will treat it will be specific: we might need to add code to check for 'exact'.
- We might want to not support screen. Again specific code for just that property.
- Putting more of the type checks using WebIDL is a good pattern.
- Why should we allow two way of writing the same things (with or without ideal?)
- We might want to extend picker preferences in the future. As an example, if all tabs of a given domain opted in getViewportMedia protections, it might be ok to allow one of this tab to ask to push user towards selecting one of these tabs over other tabs.
> The user agent MUST strongly warn the user about the dangers of self-capture.
We are in UX land, so I would go with guidelines and not mandatory statements that we will never be able to test/enforce.
--
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-924958186 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 September 2021 13:58:19 UTC