Re: [wake-lock] Introduce rate limiting to prevent wake lock abuse

By the way, the spec already addresses (1), in that it determines wake lock status depending on whether the UA has acquired or released the wake lock, regardless of what other applications do:

> Whenever user agent acquires or releases a wake lock, the user agent MUST perform the following steps for each WakeLock object:
> If WakeLock object's type attribute is not equal to type, abort these steps.
Queue a task which updates the WakeLock object's active attribute and fires an event named activechange at the WakeLock object.

But I think this should be mentioned more explicitly.

GitHub Notification of comment by andrey-logvinov
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 18 April 2018 13:06:12 UTC