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

@RichardMaher I totally agree with @martinthomson that none of this is really a service worker issue. All of what you describe is about features build on top of service workers, so the geolocation working group would most definitely be the correct location to actually pursue this.

Having said that, what you describe does sound very similar to parts of the API I sketched in https://github.com/slightlyoff/ServiceWorker/issues/745#issuecomment-149379448 (and https://gist.github.com/mkruisselbrink/d0d38b38979a37778e71, or in a version not specifically about geolocation in https://github.com/w3c/sensors/issues/73).

And yes, the new geofencing API has a lot of the same privacy and permission related problems as what you're describing. We haven't really figured out yet what to do about that (although a spec compliant implementation could not allow registering of new geofences from the background under certain circumstances, which would make adding a new geofence around the current location impossible).

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