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

Re: [wake-lock] Introduce rate limiting to prevent wake lock abuse (#124)

From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 Apr 2019 11:07:37 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-480787307-1554721656-sysbot+gh@w3.org>
> The side-channel based on the OS-level lock allows communication not only between different documents, but also between completely separate browser profiles or User Agents running on the same device. This may allow identifying users who rely on such compartamentalization for privacy.

The `active` should only show the state of a given `WakeLock` object. So even if a existing wake lock is active of the same type, the new object will only report active after it has been activated. UAs can delay resolving the promise to hide whether a wake lock was already active.

GitHub Notification of comment by kenchris
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/124#issuecomment-480787307 using your GitHub account
Received on Monday, 8 April 2019 11:07:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 8 April 2019 11:07:42 UTC