- From: Marcos Caceres <marcos@marcosc.com>
- Date: Wed, 6 Aug 2014 10:24:06 -0400
- To: "www-tag@w3.org" <www-tag@w3.org>
- Cc: Dominique Hazaël-Massieux <dom@w3.org>, Ilya Bogdanovich <bogdanovichiy@yandex-team.ru>, natasha Rooney <nrooney@gsma.com>, Mounir Lamouri <mounir@lamouri.fr>
Hi TAG, As you know, a few of us have been trying to put together some use cases and requirements for a Wake Lock API [1] for the Web. As part of that, we've hit an overlap problem between requesting a "system" wake lock - known also as a "cpu lock" on some platforms (i.e., "you can turn off the screen, but continue doing task X in the background.") and the BackgroundSync API [2] that Alex and a others are working on for SWs. We are going to defer adding the ability to do a "system" lock to the Wake Lock API for now, but it would be great for us to discuss if a "system" lock should exist at all given background sync. As a concrete use case to discuss, FireFox OS makes use of a wake lock To be able to import contacts from FaceBook, which can take a while (and the user may want to turn the screen off and put the phone back in their pocket while that is happening). It seems that FireFox OS's email app also makes use of this functionality. We would appreciate your thoughts on wether we need a "system" wake lock at all. For record keeping, this is issue #25 in our GH repo [3]. Kind regards, Marcos [1] http://w3c-webmob.github.io/wake-lock-use-cases/ [2] https://github.com/slightlyoff/BackgroundSync [3] https://github.com/w3c-webmob/wake-lock-use-cases/issues/25 -- Marcos Caceres
Received on Wednesday, 6 August 2014 14:24:33 UTC