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.

Sign up for GitHub

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

Jump to bottom

Integration in Permission API #4

Closed
dontcallmedom opened this issue Sep 12, 2016 · 4 comments
Closed

Integration in Permission API #4

dontcallmedom opened this issue Sep 12, 2016 · 4 comments

Comments

@dontcallmedom
Copy link
Member

The spec (as the 2 other specs) defines a new permission name ("accelerometer"), which I understand needs to be added to the Permission API.

Also, the link to "permission name" is broken (no matching anchor).
@alexshalamov
Copy link

Functionality related to permissions is described in Generic Sensor specification. Due to w3c/sensors#174 , there is no need to obtain permissions explicitly for Accelerometer sensor. @dontcallmedom can I close this issue?

@dontcallmedom
Copy link
Member Author

Shouldn't we wait till w3c/sensors#174 gets resolved first?

@alexshalamov
Copy link

@dontcallmedom sure.

@anssiko
Copy link
Member

anssiko commented Mar 8, 2017

We should aim to provide a solution for implementations that may want to gate this API behind a permission prompt or similar regardless of Chrome's decision. Needs to be discussed in w3c/sensors#174

@alexshalamov alexshalamov mentioned this issue Mar 31, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dontcallmedom @anssiko @alexshalamov