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

@tobie @pozdnyakov I hope you don't mind hijacking discussion :smile: could everyone answer simple two questions:

- Is `Sensor.reading === Sensor.reading` still valid requirement and must be satisfied (even when instances have different frequency hint)?
- Is it acceptable that `'onchange'` notification is out-of-sync with sensor reading modification that initiated `'onchange'` event?

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