Re: [mediacapture-screen-share] Revisit: Let getDisplayMedia() influence the default type choice in the picker (#184)

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

Sent via github-notify-ml as configured in

Received on Tuesday, 1 February 2022 16:45:26 UTC