W3C home > Mailing lists > Public > public-device-apis-log@w3.org > June 2017

Re: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency?

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Thu, 08 Jun 2017 10:04:13 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-307058954-1496916252-sysbot+gh@w3.org>
> If you sync to windows.requestAnimationFrame / VRDisplay.requestAnimationFrame, you could make "frequency" be defined in terms (times, fraction) of rAF.

Yup. I think we discussed something like this as part of one of the first issues.

> Now that even rAF can be different things, like UA hardware, VR headset, how do we device which one to sync to? If we can answer that, we might also be able to answer what we sync with in a Worker. There is a lot of talk about throttling tabs and workers in Chrome, so this might become important soon.

Can't agree more. Devil is in the details, and that's particularly true of such an API. These issues will have to be meticulously understood and addressed if we want to truly improve on the `DeviceOrientationEvent`, and not just ship a cosmetic improvement that doesn't, in fact, address the real issues.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/209#issuecomment-307058954 using your GitHub account
Received on Thursday, 8 June 2017 10:04:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC