Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations

Thanks, how about the exploration item:

>The use of only two high-level sensor permission names e.g. movement and (environment) ambient.

Was out exploration outcome to go with low-level sensor permission names such as `ambient-light-sensor`? With that as a precedence, I'm expecting we are now converging on:

* `proximity-sensor`
* `accelerometer`
* `gyroscope`
* `magnetometer`
* `orientation-sensor`

Rather than high-level sensor permission names:

* `environment-sensors`
* `motion-sensors`

FTR, I don't have a personal opinion on which way to go, but I think we should settle on something rather sooner than later, and stick with it.

As discussed in this issue, these strings are probably never a good idea to be surfaced to the UI level, rather mapped to something more sensible to the user. And that's great, and by design.

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/sensors/issues/22#issuecomment-285663269 using your GitHub account

Received on Friday, 10 March 2017 12:59:48 UTC