Open xiuqijix opened 6 years ago
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.
@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.
A note for possible future use:
To align this spec with changes in https://github.com/w3c/sensors/commit/7cea69d5b50cddf4ff1393f804db490a2b3e3b55, 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.
PermissionName definition is missing in both Proximity and Permission API spec.