Add "geolocation" wake lock

[kenchris]

@tomayac is interested in this for the GeolocationSensor.

https://docs.microsoft.com/en-us/windows/uwp/launch-resume/run-minimized-with-extended-execution

Windows also has special API for geolocation as there can

• Only be one lock at a given time
• Regular CPU "system" lock has a time limit when the device is running on battery

We could also spec that the lock would be rejected if the same global scope doesn't have an active GeolocationSensor - I think that makes sense.

This might require some spec changes in the GeolocationSensor spec as well.

Up for speccing this @tomayac ?

[tomayac]

Happy to spec this, just note that at the moment I am knees-deep in Google I/O preparations, but I keep this in mind.

[reillyeon]

It's unclear from Microsoft's documentation what the effect of acquiring this kind of wake lock is. Especially given #138 we should be careful to document the difference between this and the "system" wake lock type.

[kenchris]

It can be specced in a way that it can be implemented as just a system lock.

System locks on Windows are time limited on battery (not plugged in, discharging) but geolocation is not, as far as I can read, but it had the limitation that only one may exist

[hadriann]

Would be great if the system wake lock kept the GPS alive in the background when it is used by the Geolocation API (classic or sensor). Just as native apps do for tracking various sports activities. It's also been discussed in this issue: w3c/geolocation-sensor#22 (comment).

It would be a nice step forward for web apps in terms of capabilities.

[marcoscaceres]

Closing, as this is now out of scope for this spec. @tomayac, should we spin this issue up somewhere else? I wonder if we should just spin this up directly in http://github.com/w3c/geolocation-api/ ?

[tomayac]

@anssiko, what's your opinion here? Especially give this Geolocation Sensor issue?

[rakuco]

(just fyi, Anssi is OoO and will be back next week)