Re: [deviceorientation] Add API for requesting permission to receive device motion / orientation events (#57)

A note on scoping with my chair hat on:

As @reillyeon [pointed out earlier](https://github.com/w3c/deviceorientation/issues/57#issuecomment-447086980), DAS WG's position is this specification is superseded by the Generic Sensors family of specifications which include integration with the Permissions API. The DAS WG considers this spec to be in maintenance, and as such no new feature work per charter. The [charter](https://www.w3.org/2018/06/devices-sensors-wg-charter.html) is not super clear on this, says "fix remaining known issues and to finish" so I'm open to discussion if someone feels strongly we should add new API surface to this spec.

An alternative transition plan to browsers who are planning to unship this legacy feature sometime in the future would be to first implement (applicable parts of) the new API surface (see Generic Sensor API and related concrete sensors at https://www.w3.org/das/roadmap), and deprecate the legacy API surface only after a reasonable grace period during which web developers are recommended to migrate to the new API that provides the permission hooks and other privacy enhancements.

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

Received on Thursday, 10 January 2019 07:27:54 UTC