Re: [ServiceWorker] Expose GeoLocation to workers (#745)

It doesn't sound like you need the actual current geolocation for that usecase? You just want to know if the user is in a specific area, so adding a geofence should be enough for that, at least as it is currently specced. That still has the privacy and security aspects of course. We haven't quite worked out yet what should and shouldn't be allowed with respect to registering geofences from a service worker while there are no clients currently shown.
Also maybe the list of potential areas is too big to actually register geofences for all of them, so I agree that having a way to get the current position from a service worker could indeed be valuable. I'm not convinced that having a way to watch the current position is something that we want to expose to service workers though. Certainly not if that would mean constantly waking up/keeping up the service worker while somebodies device is moving... There are of course usecases for background location tracking, but I think some kind of API where chrome does the tracking and only passes on a complete track would be a much better API for service workers.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/745#issuecomment-140164131