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: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 May 2017 11:20:21 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304637601-1496056820-sysbot+gh@w3.org>

> Is it acceptable that 'onchange' notification is out-of-sync with sensor reading modification that initiated 'onchange' event?

I don't think it would be, though. The new task both sets the value that `sensor.x` gets and fires the event synchronously. So in the event turn where the task runs, everything is in sync.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/152#issuecomment-304637601 using your GitHub account
Received on Monday, 29 May 2017 11:20:27 UTC

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