- From: Jeffrey Yasskin <notifications@github.com>
- Date: Fri, 22 Sep 2017 16:19:54 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 22 September 2017 23:20:38 UTC
@reillyeon Sorry for being unclear. I understand @annevk as suggesting that we add a `permissions.request('accelerometer')`, where developers could only pass a subset of [`PermissionName`](https://w3c.github.io/permissions/#enumdef-permissionname)s to this `request()` function. Leaving out permissions like ["notifications"](https://w3c.github.io/permissions/#dom-permissionname-notifications) is what's not generic. I believe the [Mozilla thread](https://groups.google.com/d/topic/mozilla.dev.platform/1YdMiVQ2zaU/discussion) is talking about constraining the old [`devicemotion`](https://www.w3.org/TR/2016/CR-orientation-event-20160818/#devicemotion) events. The new Generic Sensor-based sensors already have natural places to insert the permission request, so maybe we don't need a new request function for them. ... Given that, is there value in asking developers to call a new function in order to keep using the old events? Should we just encourage them to move over to the new API instead? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/158#issuecomment-331581607
Received on Friday, 22 September 2017 23:20:38 UTC