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

@JamesTheAwesomeDude @chaals @LJWatson My heart is truly breaking :-(

The fifth birthday of this topic has come and gone yet somehow we've managed to maintain the rage; well done. By this post alone regardless the many censored redactions by the @marcoscaceres cancel culture the voice of the people is crying out in the face of shameless falsehoods of "other priotities" and "insufficient interest".

Because of this topics and the many others to fora such as StackOverflow: -
https://stackoverflow.com/questions/44233409/background-geolocation-serviceworker-onmessage-event-order-when-web-app-regain/46210408#46210408
and
https://stackoverflow.com/questions/55290691/is-there-way-to-track-user-current-location-within-service-workers-in-pwa-while/55291929#55291929

It behoves W3C to explain their rationale, nay excuses, for not responding to such legitimate and modest requests for essential PWA functionality. 

I can easily exlain to @ingenix21  why standard geolocation API is unsuitable for ServiceWorkers but we need to focus on the proven and for *5 years* unchallenged TravelManager[ solution](https://github.com/RichardMaher/Brotkrumen)

Apple has green lights and read lights to unveil background functionality to the user. User permission is an issue easily solved once we have a solution that has been at hand for FIVE YEARS.

Rule 1. Nothing happens if and instance of Chrome is not running Dadaa!

Can someone, ANYONE, please tell me why W3C aren't doing this???

If only I wasn't censored from so many forums I can certainly tell you in few words why the WakeLock and dreamtime GeoLocation sensor are completely infeasible.

How to we escalate this issue over the corruption and/or incompetence of those involved at W3C?


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/745#issuecomment-744395665