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

enumerateDevices should only provide device info permission for granted device types #645

Closed
youennf opened this issue Nov 28, 2019 · 3 comments · Fixed by #773
Closed
Assignees
Labels
PR exists privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.

Comments

@youennf
Copy link
Contributor

youennf commented Nov 28, 2019

The spec allows to expose devices through enumerateDevices after a successful getUserMedia call.
It makes sense to restrict it to either device or device type.
Per-device would be good to have but might depend on the actual browser implementation.

Per device type seems like the minimum bar.
In particular, if a user agent is asking "Allow access to camera", it does not make real sense to leak microphones.

@bradisbell
Copy link

I often work with several cameras and audio devices simultaneously. In these scenarios, I don't think a per-device info grant makes sense, as that prohibits the application from showing a list of devices to the user to choose from.

We already have the problem of prompting the user what initial device they'd like to use. While for many video conferencing style applications, leaving the default device is appropriate, more advanced use cases really do require this device information exposed to the application. It's my understanding that the upcoming Permissions API will help with this, as we will be able to request what's needed up-front?

In either case, I think the suggestion of limiting to device type would be fine.

@youennf
Copy link
Contributor Author

youennf commented Jan 16, 2020

Issue specific to enumerateDevices. Might want to consider devicechange as a separate issue.

@youennf youennf self-assigned this Jan 16, 2020
@dontcallmedom dontcallmedom added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Mar 20, 2020
@w3cbot w3cbot added privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. and removed privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. labels May 22, 2020
@jan-ivar jan-ivar added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Oct 9, 2020
@w3cbot w3cbot removed the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Oct 13, 2020
@jan-ivar
Copy link
Member

jan-ivar commented Nov 9, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR exists privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants