On Jul 15, 2015, at 4:39 AM, Jonas Sicking <[email protected]> wrote: > > Yes. We should definitely make the default behavior that background > pages automatically stop receiving GPS and orientation data. > > But then allow such pages to explicitly opt in to continue receiving > such data in the background. Possibly by using something like [1] to > allow the page to grab a "geolocation"/"orientation" wakelock. > > [1] http://w3c.github.io/wake-lock/ > > / Jonas
Very interesting. To summarize my understanding: • FxOS apps have window.navigator.requestWakeLock(type) and we could look at adding a 'geolocation' type. •• App must be foreground, and geo tracking apps on iOS and Android do not require this. •• Not for Firefox browser • The w3c wake-lock doc partially touches on the geolocation use-case here: http://www.w3.org/TR/wake-lock-use-cases/#keeping-the-system-awake This mentions keeping the system awake for short periods for work to complete. This is not how background geolocation works on iOS or Android; in a screen-off state, geolocation can continue indefinitely on these platforms. • This topic will come up again as we look at geofencing, which many applications of it are for the screen-off power state. Undecided ATM if geofencing (when used with a small movement tolerance) is an appropriate hack workaround for background geo. _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
