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

result of enumerateDevices when there is no origin #417

Closed
guidou opened this issue Nov 14, 2016 · 4 comments
Closed

result of enumerateDevices when there is no origin #417

guidou opened this issue Nov 14, 2016 · 4 comments
Assignees

Comments

@guidou
Copy link

guidou commented Nov 14, 2016

Sections 9.2 and 9.3 establish a security model based on a page's origin.
Device IDs are unique per origin and so on.
However, behavior is not defined for the case when there is no origin. For example, what should happen if a user calls enumerateDevices from a JavaScript console and the page is "about:blank", or something equivalent, without any defined origin?

@ShijunS
Copy link
Contributor

ShijunS commented Dec 3, 2016

For case associated with an origin, the deviceID persists as with other storage such as cookies.  For cases without origin, I'd expect no cookies are stored, so the deviceID should be unique per session and will not be persistent across sessions. Would that make sense?

@guidou
Copy link
Author

guidou commented Dec 5, 2016

That would make sense.
Do you think rejecting the promise would make sense too?

@ShijunS
Copy link
Contributor

ShijunS commented Dec 5, 2016

I think we should treat the API like all others, for example, it'd be nice to keep the JavaScript console as a valid test option for web developers.

@alvestrand
Copy link
Contributor

No change to the spec needed; closing.

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

No branches or pull requests

3 participants