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

Re: [screen-wake-lock] explainer: Expand on why WakeLock.request() still requires an argument. (#288)

From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
Date: Wed, 23 Sep 2020 14:46:18 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-697474964-1600872377-sysbot+gh@w3.org>
When I think of "keeping a device awake", it's mostly the screen I'm thinking about. Having to explicitly tell you "yes, I mean the screen" is strange and weird. If I were doing something unusual, like requiring the CPU be kept awake, then sure, maybe I should provide extra indication. But for the screen, it should just be the default.

GitHub Notification of comment by domenic
Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/pull/288#issuecomment-697474964 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 September 2020 14:46:20 UTC

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