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

Going back to the original issue reported here: looking at and, 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 using your GitHub account

Received on Friday, 18 October 2019 08:14:39 UTC