- From: Michael Cooper <cooper@w3.org>
- Date: Wed, 11 Nov 2020 12:41:45 -0500
- To: public-apa@w3.org, Fuqiao Xue <xfq@w3.org>
- Cc: reillyg@google.com, anssi.kostiainen@intel.com
- Message-ID: <7254e144-0d03-c8fe-532a-82d2898af7b6@w3.org>
Thanks for requesting review. The APA WG has no comments on this spec. Michael > Hi, > > The Devices and Sensors WG plan to publish CR of the Screen Wake Lock > API. Here's the current ED: > > https://w3c.github.io/screen-wake-lock/ <https://w3c.github.io/screen-wake-lock/> > > This document specifies an API that allows web applications to request a > screen wake lock. Under the right conditions, and if allowed, the screen > wake lock prevents the system from turning off a device's screen. > > Changes since the last CR: > https://w3c.github.io/screen-wake-lock/#changes-20171214 <https://w3c.github.io/screen-wake-lock/#changes-20171214> > > I have worked through the FAST Checklist and this specification: > > * defines an API > * does not allow visual rendering of content > * does not provide author control over color > * does not provide features to accept user input > * does not provide user interaction features > * does not define document semantics > * does not provide time-based visual media > * does not provide audio > * does not allow text content > * does not create objects that don't have an inherent text > representation > * does not provide visual graphics > * allows time limits (user agents and the underlying OS may time limit a > wake lock given the battery status, or even disallow wake locks in the > case a power saving mode is activated) > > Most of the accessibility concerns are tangential to this spec, but if > you do find any issues, please file them at > https://github.com/w3c/screen-wake-lock/issues <https://github.com/w3c/screen-wake-lock/issues> > > Thanks, > > Fuqiao
Received on Wednesday, 11 November 2020 17:41:48 UTC