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

Re: [wake-lock] In obtain permission: don't co-opt resultPromise - it's creating a custom permission model (#198)

From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Fri, 18 Oct 2019 08:14:37 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-543589651-1571386476-sysbot+gh@w3.org>
Going back to the original issue reported here: looking at https://w3c.github.io/wake-lock/#permission-algorithms and https://w3c.github.io/permissions/#requesting-more-permission, both seem very similar. The Wake Lock version has some extra steps for checking if the request was triggered by user activation though.

Is there anything we can do at the moment to the Permissions spec, or shall we keep things as they are?

As for the issue with workers, I've filed #246 to track it.

GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/198#issuecomment-543589651 using your GitHub account
Received on Friday, 18 October 2019 08:14:39 UTC

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