- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Apr 2017 08:54:45 +0000
- To: public-device-apis-log@w3.org
> Yes, I think it should be "idled". Well, "stopped" in that case. But then that's weird as first state. I don't want to Bikeshed this into eternity, though. > Will there be an onidled event handler as well? No, because it's sync. > Hmm, old cached readings would probably be quite bad though, as many changes can have happened since I used the sensor last and mixing those with new readings will introduce errors. What is the use-case for that? Saving battery, e.g. for geolocation. Maybe this needs its own API, though. Tracked here: https://github.com/w3c/sensors/issues/89 -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/160#issuecomment-291085290 using your GitHub account
Received on Monday, 3 April 2017 08:54:51 UTC