- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jan 2020 08:29:46 +0000
- To: public-device-apis-log@w3.org
@npdoty, thanks for the update, very helpful. Re use cases, I think WebVR/XR used to be the most demanding one. It has a strict motion-to-photon latency requirement in the ballpark of <20 ms to avoid motion sickness. That said, the Sensor APIs were used to polyfill those APIs and now that there's a dedicated WebXR Device API perhaps that use case is not that strong for Sensor APIs anymore. Anyone have use cases in mind that would be compromised if we'd introduce the two proposed mitigations? Any concerns on feasibility of implementation? -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/85#issuecomment-574061390 using your GitHub account
Received on Tuesday, 14 January 2020 08:29:48 UTC