W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2016

Re: [whatwg] Background Geolocation for Progressive Web-Apps

From: Richard Maher <maherrj@googlemail.com>
Date: Fri, 2 Dec 2016 09:57:11 +0800
Message-ID: <CABvL1xr1KKXH4Z7LN8CfZv0xF9j0gx8SH2vxfhVNHK1TeC54Gg@mail.gmail.com>
To: Karl Dubost <karl@la-grange.net>
Cc: WHAT Working Group <whatwg@whatwg.org>
On Fri, Dec 2, 2016 at 9:41 AM, Karl Dubost <karl@la-grange.net> wrote:

>
> Le 2 déc. 2016 à 08:53, Richard Maher <maherrj@googlemail.com> a écrit :
> > The main goal of background geolocation reporting
>
> Previous related threads:
> https://groups.google.com/forum/#!topic/mozilla.dev.
> geolocation/D5UXf-N3JfU

Chalk and Chees. But I do want wakelock functionality as well.

>
> https://lists.w3.org/Archives/Public/public-geolocation/2016Feb/0016.html

Since then the Geofencing API has died

>
> https://lists.w3.org/Archives/Public/public-geolocation/2016Feb/0017.html

Well worth reading

>
> https://lists.w3.org/Archives/Public/public-geolocation/2016Feb/0010.html

 Yep

>
> https://groups.google.com/forum/#!topic/mozilla.dev.
> geolocation/UXkd3Tz1GPc

Unrelated. I managed to get Chrome's implementation of the GeoFence API
canned and a wakeLock is not battery friendly and not secure except for
constantly foreground APPs such as navigation.
Received on Friday, 2 December 2016 01:57:44 UTC

This archive was generated by hypermail 2.3.1 : Friday, 2 December 2016 01:57:44 UTC