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

I'm going to close this as addressed. 

Right now, per spec, the we always call into "acquire a wake lock", which always asks the OS to get the lock. Further, we have a note that makes it clear that:

> The acquire a wake lock algorithm may ultimately be unable to acquire a lock from the operating system, but this is indistinguishable from a successful lock acquisition to avoid user fingerprinting (failure to acquire a lock can indicate low battery levels, for example).

 

-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/124#issuecomment-900787099 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 August 2021 03:36:04 UTC