Requesting wake locks from Workers

[reillyeon]

For all intents and purposes a wake lock requested from a (dedicated) worker is the same as one requested by the frame that owns the worker but especially for system wake locks which are likely being held to a computation continues uninterrupted it makes sense to have that managed by the worker performing the computation.

This does raise a question for implementations on how to determine when a worker script has become unresponsive.

[kenchris]

OK, adding this now is quite simple but we have a few things to handle later

• Feature policy (not handled by feature policy spec yet): Feature-Policy and Workers webappsec-permissions-policy#207
• Permission Prompt - you suggest a requestPermission() method for the Geolocation Sensor, but I didn't fully understand how that would work: Expose GeolocationSensor to dedicated workers geolocation-sensor#37 (comment)

[kenchris]

Additional info here: w3c/sensors#388

[kenchris]

So this should work now by using the permission spec, but should we still add a requestPermission()? and where should that then live? on the WakeLock object?

[reillyeon]

I see no harm in adding a requestPermission() function that is a wrapper around the algorithm from the permissions spec. It should be able to take a wake lock type as a parameter so either be a static function on WakeLock with extra parameters or inherit the parameters from the WakeLock that is provided as this.

[kenchris]

It is static on notification spec as well as on device orientation and motion - so let's go with that

How does this look?

[Exposed=Window] static Promise<PermissionState> requestPermission(WakeLockType type)

[reillyeon]

Seems reasonable.

[mrunalk]

Any reason why requestPermission() has to be static in Wakelock's case. in case of Notifications API may be there are many different types of notifications but for WakeLock we are dealing with only two types of wakelocks. I would prefer non-static version which inherits parameters.

[kenchris]

@mrunalk yes

• consistency with the web platform
• you don't need to instantiate an object you never will use as you intent to do it on a worker