W3C home > Mailing lists > Public > public-device-apis-log@w3.org > December 2018

Re: [wake-lock] Give advice on how UAs should infer consent to take a wakelock (#140)

From: Feross Aboukhadijeh via GitHub <sysbot+gh@w3.org>
Date: Sun, 23 Dec 2018 03:35:01 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-449612061-1545536099-sysbot+gh@w3.org>
Why do "geolocation in the background" vs "geolocation in the foreground" need to be distinguished?

I believe that a site with geolocation permission that is open in a tab already has the ability to continuously poll for geolocation.

Adding a System Wake Lock just allows the site to ensure that it isn't unloaded by the browser, but there are other ways to accomplish this already, including keeping a WebRTC data channel open, playing a silent audio file, etc.

In other words, I don't think this API actually enables anything that wasn't already possible, just makes it a bit easier to accomplish and provides a better guarantee that the CPU will stay active.

Now, if we're allowing a site to wake itself up and get geolocation *after the tab has already been closed by the user* (say by using a service worker), then I believe a separate permission would be warranted. But this API isn't doing that.

GitHub Notification of comment by feross
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/140#issuecomment-449612061 using your GitHub account
Received on Sunday, 23 December 2018 03:35:02 UTC

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