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

Missing PermissionName definition #32

Open
xiuqijix opened this issue Jan 22, 2018 · 3 comments
Open

Missing PermissionName definition #32

xiuqijix opened this issue Jan 22, 2018 · 3 comments

Comments

@xiuqijix
Copy link

PermissionName definition is missing in both Proximity and Permission API spec.

@riju
Copy link
Contributor

riju commented Jan 23, 2018

Speculatively the PermissionName for this can be "proximity-sensor" , but we can bikeshed about the name when the time is right.
We will add the Permission hook when we are close to implementing it.

@anssiko
Copy link
Member

anssiko commented Jan 23, 2018

@kaixinjxq @riju, thanks for your comments.

Assuming positive feedback from the motion sensors Origin Trial in Chrome, we should reuse the same Permissions API integration pattern for this spec too.

Let's leave this issue open until we get that feedback.

@anssiko
Copy link
Member

anssiko commented Mar 1, 2018

A note for possible future use:

To align this spec with changes in w3c/sensors@7cea69d, use the following prose:

The <a>Proximity Sensor</a> has an associated [=sensor permission name=]
which is <a for="PermissionName" enum-value>"proximity-sensor"</a>.

And upstream the proposed "proximity-sensor" string to the Permissions API.

Let's keep this open, and revisit if implementers' interest emerge.

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

3 participants