- From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Sep 2017 08:07:26 +0000
- To: public-device-apis-log@w3.org
>From https://github.com/w3c/sensors/issues/209#issuecomment-305598188 it follows that setting sampling frequency directly from JS API does not look like a feasible option: > An application that sets a sampleFrequency can never actually know if the device it's running on is actually capable of that sampleFrequency, which means no algorithm could be written that expects reliability from sampleFrequency. So, the JS API just sets the reporting frequency and then the UA requests an appropriate sampling frequency from the underlying platform. The https://github.com/w3c/sensors/pull/290 has introduced the related definitions and clarifications to the spec, accordingly to terminology proposed at https://github.com/w3c/sensors/issues/209#issuecomment-305501222. -- GitHub Notification of comment by pozdnyakov Please view or discuss this issue at https://github.com/w3c/sensors/issues/209#issuecomment-333060418 using your GitHub account
Received on Friday, 29 September 2017 08:07:18 UTC