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

> to me more clear: slowSensor.x is not (always) equal to fastSensor.x.

Well, yes. That's an effect of the caching. My question is: is this desirable, given (1) none of the other behavior we agree we want to add depend on this, and (2) `===` was one a requirement (see #8).

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/152#issuecomment-304274073 using your GitHub account

Received on Friday, 26 May 2017 12:47:09 UTC