W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2018

Re: [whatwg] Expose GeoLocation to workers #745

From: Richard Maher <maherrj@googlemail.com>
Date: Sat, 17 Feb 2018 08:48:35 +0800
Message-ID: <CABvL1xrdpRs=Lb-dUuaJ0bsPQdVMUQDeKcR-0o33Ygj2N8FNsg@mail.gmail.com>
To: Mauro Pereira Junior <mauropereirajr@gmail.com>, Natan SÄ…gol <m@merlinnot.com>, Marcos Caceres <marcos@marcosc.com>, WHAT Working Group <whatwg@whatwg.org>, service-worker-discuss@chromium.org
Yeah that's what I thought :-(

On Tue, Feb 13, 2018 at 8:12 AM, Richard Maher <maherrj@googlemail.com>
wrote:

> Regarding the very recent comments following on from: -
> https://github.com/w3c/ServiceWorker/issues/745#issuecomment-344128148
>
> Can any of you please explain what is wrong with the complete POC solution
> here: -
> https://drive.google.com/drive/folders/0B7Rmd3Rn8_hDNW1zSWRoXzBTclU
>
> If the proposed solution is somehow deficient or not fit for purpose
> please let me know!
>
> I believe the permissions/user-visibility conundrums to be the only loose
> end.
>
> Please also note the plethora of use cases detailed by numerous people
> over the years that can be found here: -
> https://github.com/w3c/ServiceWorker/issues/745
>
> I do not understand Marcos' claim that there is little browser interest
> when Edge and Chrome are waiting on a specification to implement. Firefox
> already allows tracking of users in the background today.
>
> Cheers Richard Maher
>
Received on Saturday, 17 February 2018 00:49:12 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:45 UTC