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

According to an [article](https://medium.com/@firt/pwas-on-ios-12-2-beta-the-good-the-bad-and-the-not-sure-yet-if-good-a37b6fa6afbf#1e1f) discussing iOS 12.2 beta features:
>* Accessing sensor APIs is now disabled by default, so no accelerometer, gyroscope or magnetometer APIs are working unless the user enables a Settings option under “Safari”

Assuming this beta feature will ship in stable, it will diverge from [Blink's plan](https://github.com/w3c/deviceorientation/issues/57#issuecomment-447430709) to allow access to the existing level of precision and frequency by default.

A possible impact on iOS users is that websites start to show bespoke modal dialogs to iOS Safari users that ask to enable the "Motion & Orientation Access" option in iOS Settings (similarly to those "Add to homescreen" bespoke dialogs).

That seems like a suboptimal UX for iOS users, so I'm interested in finding a consensus position among implementers that would enable a better UX for all implementers. If `requestPermission()` is a fix all implementers can live with, we can make a case that it is needed to "fix a remaining known issue" in the API and see if anyone has concerns, and spec it. As said, the charter has some leeway in this regard, so we could likely pull that off with all implementers on board.

Seeking feedback from @cdumez and @reillyeon (with his Blink hat on).

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

Received on Tuesday, 29 January 2019 09:16:26 UTC