W3C home > Mailing lists > Public > public-device-apis-log@w3.org > October 2019

[wake-lock] Figure out what to do with workers and permission requests (#246)

From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Fri, 18 Oct 2019 08:14:18 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-508924954-1571386456-sysbot+gh@w3.org>
rakuco has just created a new issue for https://github.com/w3c/wake-lock:

== Figure out what to do with workers and permission requests ==
This was originally discussed in #198. PR #237 removed `requestPermission()` from the API, but our [obtain permission](https://w3c.github.io/wake-lock/#permission-algorithms) algorithm requires user activation if the wake lock permission is set to "prompt".

[One proposal](https://github.com/w3c/wake-lock/issues/198#issuecomment-539826887) in #198 says _"we move it [requestPermission()] to the content process and look at how Push API handles this, as they seem somewhat related in terms of permission model"_.

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/246 using your GitHub account
Received on Friday, 18 October 2019 08:14:20 UTC

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