- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Aug 2021 21:53:57 +0000
- To: public-device-apis-log@w3.org
> > Hmm, given the discussions in [w3c/permissions#247](https://github.com/w3c/permissions/pull/247) and that Chromium does implement this integration with the Permissions API, is there a specific reason for changing course here?
>
> My concern is that we have a permission that’s not tied to a permission UI, so it doesn’t fit the purpose of the Permission spec. So, `query()`ing it is kinda meaningless as it always returns “granted”.
In [w3c/permissions#247](https://github.com/w3c/permissions/pull/247) @martinthomson agreed that there's no substantial harm if `query("screen-wake-lock")` always returns true. As discussed there, this is about making sure the API design is flexible enough to support adding scenarios where permission may not be granted in the future. If we update the permission text I think we should acknowledge this as an area of future development based on additional implementation experience and that the `"screen-wake-lock"` permission identifier is a placeholder for that future work.
--
GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/324#issuecomment-906768740 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 August 2021 21:53:58 UTC