- From: Rich Tibbett via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Feb 2019 06:08:34 +0000
- To: public-device-apis-log@w3.org
Fundamentally, I want to be clear this specification was never designed to be used for VR/AR. The fact this API is being currently used for AR/VR tracking, and that is therefore considered one of its use cases, is due to real VR/AR APIs not being implemented in WebKit (they are implemented in all other mobile browsers). What we are actually losing is the ability to deliver all the other use cases where a default level of coarse-grained data is still very useful. That includes all progressive enhancement features, motion-based animations and custom gestures as a basic user input (e.g. shake or tilt to sit alongside touch, keyboard and mouse inputs). So this is a final request that these use cases are, firstly, acknowledged as being in operation today. Secondly, that there is an understanding these uses will disappear from the web. And, thirdly, that these use cases do not simply get discarded as collateral damage when talking about VR/AR tracking or precision more suited to other APIs. Longer term there is hope that a default coarse-grained level of access will continue to be made available (through e.g. the Generic Sensors API) but that is of little consolation for those that rely on some form of sensor access being available today. Given more time than is currently available we could resolve all these issues and conflicts in the best interests of everyone. -- GitHub Notification of comment by richtr Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-459939214 using your GitHub account
Received on Saturday, 2 February 2019 06:08:35 UTC