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

>> 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.

Sorry, I confused option 2 and 3 here (I thought they were ordered chronologically, not in order of increasing implementation cost and complexity).

So: option 2, we're good to do; option 3 we don't have consensus on (we might end-up doing so, but I'm not sure we want to do so yet).

That is:

per instance reporting frequency: yes.
per instance reading cache: no.






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

Received on Monday, 29 May 2017 11:25:51 UTC