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:19:09 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-697430310-1600870748-sysbot+gh@w3.org>
> Not requiring an argument would make it difficult to support requesting
other locks in an intuitive way

I don't understand this. Why not just make the default screen, then if you do pass an argument, you can get some other type of lock? You call it "not ergonomic or intuitive", but I think defaults are a pretty well-known pattern.

GitHub Notification of comment by domenic
Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/pull/288#issuecomment-697430310 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:19:11 UTC

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