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

> Browser-based content and embedded web view content in native applications will cease operation in all of the following use cases:
>
>* Games and gaming
>* Navigation
>* Virtual Reality
>* Augmented Reality
>* 360 viewers (videos, panoramas)
>* 3D scanning
>* Gesture recognition
>* Step counters
>* Physical activity monitoring
>* Sleep monitors

How many of these things are implemented as web apps/views? And why would requiring them to ask permission be that big of a deal? There is exactly zero people who should be able to access any of this data without asking for permission, in my opinion. And I honestly couldn't care less how many business models or apps would be affected by having to ask permission. If the app is scared of asking for permission first, I don't want them having my data anyway.

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

Received on Wednesday, 9 January 2019 20:53:28 UTC