- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Feb 2022 16:45:24 +0000
- To: public-webrtc-logs@w3.org
> Question: why are you assuming the solution should be to use the same standard property but with a non standard 'monitor' value? Because it minimizes the logic that has to be written. Why would Chrome want to code two parallel codepaths that accomplish virtually the same thing? > Using a non standard value might become a compatibility issue as other browsers may start breaking pages by rejecting instead of ignoring. Is there a good reason for the spec to mandate the the user agent MUST reject? Can't we mandate MAY ignore? After all, the user can **always** select a surface type other than the `ideal` one, so ignoring the `ideal` surface should be reasonable from the POV of all entities (UA, application, user). > SHOULD ignore would leave that to UA territory, which is more flexible (though a strange API). I think that `MAY ignore` is less strange than `SHOULD ignore`, but I'd accept either. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/184#issuecomment-1027049811 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 16:45:26 UTC