W3C home > Mailing lists > Public > public-geolocation@w3.org > October 2022

Re: [geolocation-api] Background Geolocation (#131)

From: Tom333Trinity via GitHub <sysbot+gh@w3.org>
Date: Wed, 05 Oct 2022 07:42:19 +0000
To: public-geolocation@w3.org
Message-ID: <issue_comment.created-1268066964-1664955629-sysbot+gh@w3.org>
@UVLabs please see my Brotkrumen PWA at https://richardmaher.github.io/Brotkrumen/TravelManager.html

Problems: -
1) There's some CSS issue(s) on Safari. If someone can teel me why that's great otherwise use Android
2) Not all browsers on Android support Wake Lock which is needed 'cos Backgroud Geolocation is Vorbotten
3) You need to have your own Google Maps API key as they frown on publishing mine

Having said that, it works like a charm (as long as you move about a bit) and the code can be found
[here](https://github.com/RichardMaher/Brotkrumen)

All the Browser/UA  has to implement is the TravelManagerPolyfill and we're done!

@reillyeon you are wrong again :-(

The Browser/UA is *ALWAYS* in control of the geolocation change events! It can throttle them, hide them, make sure user visibility is appropriate, in fact do anything and *EVERY* iOS and Android implementations *trust* there browsers.

But sadly, no one will ask a techichnical questions or challenge the TravelManager design and instead just spread FUD :-(

Apart from user visibility and approval it's good to go! Why not?


-- 
GitHub Notification of comment by Tom333Trinity
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/131#issuecomment-1268066964 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 October 2022 07:42:21 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 5 October 2022 07:42:21 UTC