- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Wed, 05 Feb 2014 11:58:09 +0100
- To: public-web-mobile@w3.org
Hi, Someone just posted a proposed API to manage the "standby" mode of mobile devices, keeping them from e.g. locking / turning the screen off: http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0001.html Beyond the specific API proposal, the spec lists a number of simple use cases, which seem reasonable to me: > Long running websites > A user visiting a website that contains an embedded HTML5 video that > does not play in full screen on the device or a long running visual > animation. This video , or animation, may be longer than the device’s > current standby timeout value. > The web application may adjust the device standby timeout to provide a > better experience > > Games that don’t require direct touch or peripheral input > A user may engage in a web driven game that uses a sensor input on a > device. For example, a jump game driven by an accelerometer where the > user must tilt the device to play the game. Again, the duration of > gameplay may exceed that of the device standby timeout value. > > > Navigation > A user may wish to utilize a web application containing map feat > ures while operating a vehicle. The device may enter standby due to > prolonged periods of inactivity. In addition, both Firefox(OS?) and Chrome Apps propose a similar API: https://developer.mozilla.org/en-US/docs/Web/API/Navigator.requestWakeLock https://developer.chrome.com/extensions/power.html I'm interested to hear what the group thinks of the usefulness of getting work started on such an API (for in-browser usage), and in particular, if implementors would likely implement and ship such an API in their browser. Dom
Received on Wednesday, 5 February 2014 10:58:28 UTC