- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Feb 2022 14:44:31 +0000
- To: public-webrtc-logs@w3.org
> 3\. but also (ii) allow `ideal: 'monitor'` to trigger the old behavior. Question: why are you assuming the solution should be to use the same standard property but with a non standard 'monitor' value? If this is expected to be a temporary thing, using a separate property has benefits: - Using a non standard value might become a compatibility issue as other browsers may start breaking pages by rejecting instead of ignoring. - A separate property makes it clear this is non standard. - A separate property will not violate any spec. - A separate property allows more flexibility in terms of API shape and feature detection (navigator.mediaDevices.defaultToScreenCapture?). If, in the long run, Chrome identifies it needs 'monitor', this might well have an impact on other browsers: they might need to implement some form of 'monitor' as well for the exact same reasons. At that point, the spec & API could be updated. But I hope we agree that our current evaluation is that 'monitor' will be a temp thing and that we should design API based on this assumption. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-1026918753 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 February 2022 14:44:32 UTC