- From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 May 2017 07:21:37 +0000
- To: public-device-apis-log@w3.org
Given that we do not bind [`onchange` notification to rAF](https://bugs.chromium.org/p/chromium/issues/detail?id=715872) anymore it could be that we do not need to invent a new API for reporting readings at > 60 Hz frequency . I'm now testing how performance in Chromium is affected if `onchange` notification from a Senor is send at 120 Hz. -- GitHub Notification of comment by pozdnyakov Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-302629101 using your GitHub account
Received on Friday, 19 May 2017 07:21:48 UTC