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

Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Tue, 30 May 2017 07:07:21 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304792802-1496128039-sysbot+gh@w3.org>
@tobie, PR #210 has been updated to reflect the consensus position, quoting it here for clarity:

>**Option 2**
>All Sensor objects point to the same data but the change event fires at different intervals on the different objects as specified in their respective initialization options.
>* objects are still not decoupled from each other
>* frequency at which sensor.x is updated still may vary arbitrary
>* onchange notification is not synced with returned data update

Could you review #210 and let us know if you have any concerns. Thanks!

GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/sensors/issues/152#issuecomment-304792802 using your GitHub account
Received on Tuesday, 30 May 2017 07:07:27 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:54 UTC