- From: Kis, Zoltan <zoltan.kis@intel.com>
- Date: Fri, 23 May 2014 17:43:26 +0300
- To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
- Cc: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>, Dave Raggett <dsr@w3.org>, "public-sysapps@w3.org" <public-sysapps@w3.org>
On Fri, May 23, 2014 at 2:30 PM, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote: > On 23 May 2014, at 12:02, Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com> wrote: > >> I wonder why Idle (power management, keep the display on etc) has so little interest. There is a lot of developer interest in that, judging from feedback on mailing lists etc, and we definitely need something like that in Crosswalk/Tizen (we have a Tizen extension today). Should it be done under power management standardization? Both 'knowing idle' and 'keep display on' are use cases for that. "Idle" is not a good name. > > Indeed there’s interest toward the “keep the display on” API in the wider web community. However, this poll was aimed at the SysApps’ group participants, so it does not necessarily reflect the interests of the wider community. > > And actually, I think the Idle API entry in the poll derived from the SysApps Charter is backwards: “an API to be notified when the user is idle”. This is different: provides opportunity to do some of the heavy things while the user does not need immediate performance. This is not related to power policies: the system knows when to apply power policies, this does not affect that. > > Have you seen demand for this type of API as well? > > Specifically to the “keep the display on” API, the current sentiment seems to be it should go to either the Device APIs or to the HTML WG. There’s good momentum building behind that deliverable. This is a request for power policy exemption. It should indeed go where power related things are standardized. Best regards, Zoltan
Received on Friday, 23 May 2014 14:43:54 UTC