W3C home > Mailing lists > Public > public-device-apis-log@w3.org > August 2016

[sensors] Clarifying the behavior of suspending or pausing sensors upon inactivity.

From: Bryan B via GitHub <sysbot+gh@w3.org>
Date: Tue, 23 Aug 2016 21:16:53 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-172808980-1471987011-sysbot+gh@w3.org>
bbernhar has just created a new issue for 
https://github.com/w3c/sensors:

== Clarifying the behavior of suspending or pausing sensors upon 
inactivity. ==
 As an important power saving measure for potentially high frequency 
sensors, previous implementations of the sensors API could 
"deactivate" upon signs of inactivity (such as switching to another 
tab or minimizing the window). The Generic Senor API spec offers no 
guidance on whether or not this behavior should continue to exist. I 
see there is an opportunity to ensure uniformity between browsers, 
along with more predictability of this benefit for users.

If not, it could be further clarified to be _implementation defined_ 
or perhaps expanded upon by suggesting it to be more explicitly 
handled (e.g. `Sensor::Suspended`) for a all or per sensors basis.



Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/124 using your GitHub account
Received on Tuesday, 23 August 2016 21:17:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:34:21 UTC