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: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 May 2017 11:04:09 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304634945-1496055848-sysbot+gh@w3.org>
> I not sure how you've read this from that comment, tbh.

I treated "(1) none of the other behavior we agree we want to add depend on this, and (2) === was a requirement (see #8)." as a kind of stopper for option 3. If it was not the case,  I'm happy to proceed with option 3.

@alexshalamov I'd prefer `sensor1.reading != sensor2.reading` but than reading update and `onchange` events synchronized for each Sensor object.

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

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