- From: Rich Tibbett via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Jan 2019 07:45:59 +0000
- To: public-device-apis-log@w3.org
There are many softer approaches to be explored here as opposed to implementing a black-and-white “on/off” switch straight out of the gate. Following your current course will effectively destroy nascent VR/AR/360/gaming companies and industries and pretending otherwise is silly. I want to avoid a cliff-edge scenario where access to these sensors would change overnight without proper planning — particularly in browsers where no platform-alternative browser engines exist. For that purpose there are many many intermediate steps, recommended in the cited papers - before you need to implement on/off switches for an 8+ year old API. Jumping straight for that approach is incredibly hostile to web developers. Have you evaluated the full impact that would have? That is the purpose of the summary above. -- GitHub Notification of comment by richtr Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-451848170 using your GitHub account
Received on Monday, 7 January 2019 07:46:00 UTC