Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note relationship to requirements of Screen Capture #3

Open
foolip opened this issue Jul 23, 2021 · 2 comments
Open

Note relationship to requirements of Screen Capture #3

foolip opened this issue Jul 23, 2021 · 2 comments

Comments

@foolip
Copy link
Member

foolip commented Jul 23, 2021

https://w3c.github.io/mediacapture-screen-share/#dom-mediadevices-getdisplaymedia says:

The user agent MUST let the end-user choose which display surface to share out of all available choices every time, and MUST NOT use constraints to limit that choice. Instead, constraints MUST be applied to the media chosen by the user, only after they have made their selection. This prevents an application from influencing the selection of sources, see § 5.3 Unconstrained Display Surface Selection for details.

While preferCurrentTab won't limit which display surfaces are possible to chose, it will influence which surface is easiest to chose.

In a literal reading I don't think there's a willful violation (which would be OK but not great) but it is still worth a note explaining how this fits together. Maybe link back to that spec and affirm that the requirement to not use constraints still applied, but that an influence of UI order is happening.

@alvestrand
Copy link

A relevant open issue on w3c/mediacapture-screen-share#184

There's not consensus among participants that the absolute ban on influencing user choice was a rational and defensible decision.

@foolip
Copy link
Member Author

foolip commented Jul 23, 2021

Thanks for linking! If the WG / editors can't agree on a change for https://w3c.github.io/mediacapture-screen-share/ and it seems like preferCurrentTab requires ignoring some of its normative requirements, then a willful violation in https://wicg.github.io/prefer-current-tab/ would be the clearest way to deal with it I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants