W3C home > Mailing lists > Public > public-device-apis-log@w3.org > September 2020

[system-wake-lock] Request for System Wake Lock use cases (#4)

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Tue, 29 Sep 2020 10:05:15 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-710959672-1601373914-sysbot+gh@w3.org>
anssiko has just created a new issue for https://github.com/w3c/system-wake-lock:

== Request for System Wake Lock use cases ==
[Following the announcement to split the wake lock capability into two](https://lists.w3.org/Archives/Public/public-device-apis/2020Feb/0011.html), the Devices and Sensors WG is soliciting the System Wake Lock API use cases to ensure the spec work [started in 2015](https://www.w3.org/TR/2015/WD-wake-lock-20150212/) addresses the right use cases the right way.

Anyone can help (including folks who are not participants of the group) by [opening a new issue](https://github.com/w3c/system-wake-lock/issues/new) in this repo describing their use case(s) they feel cannot be realized without this capability.

Here's an example use case input:
- Fitness App #2 by @CheloXL 

With more such compelling use cases at hand the group is committed to reinvigorate the spec work in its scope and collaborate with browser vendors to ensure their perspectives are considered.

Before the actual spec work, the group may write an explainer ([example](https://github.com/w3c/screen-wake-lock/blob/gh-pages/explainer.md)) that synthesizes this input from various stakeholders and guides the actual spec work.

Please view or discuss this issue at https://github.com/w3c/system-wake-lock/issues/4 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 September 2020 10:05:17 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:58 UTC