On Android and iOS, getting GPS in the background is not a default behaviour of the APIs ( a backgrounded app will stop getting the GPS). On Android, to do this you must explicitly write your GPS request code as a service, and on iOS, I won't detail the steps, but they are onerous.
It is a problem that the default behaviour of the web api is the opposite on FxOS. And on Fennec, backgrounding Fennec while a watch request is running will continue using location. Chrome will not do that. Web developers may want to write web apps that continue to track locations when the app is backgrounded as a feature of the app, but this is an exceptional case. The default is that they don't want to do this, and writing extra code for the de-facto default behaviour seems wrong. Cross-posting to dev-geolocation, I am going to move the discussion there as it goes beyond foxfooding. > On Jul 10, 2015, at 8:26 PM, Michal Purzynski <mic...@mozilla.com> wrote: > > How about > > Background Web pages cannot use the GPS constantly > > Background of installed apps can but if they abuse the privilege user is > notified. She can choose to not be notified about this particular app in the > future. > > On Jul 11, 2015 2:04 AM, "Thomas Daede" <tda...@mozilla.com> wrote: > On 07/10/2015 04:58 PM, Eitan Isaacson wrote: > > > 2. Installed apps can be trusted to pause/resume themselves. > > Except that the whole reason this thread was started was because an > installed app was not pausing itself correctly. So some mitigation would > be nice, better than seeing a tiny droplet icon in your status bar, > opening the app switcher, and closing every app until you see the icon > go away. _______________________________________________ dev-geolocation mailing list dev-geolocation@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-geolocation
