W3C home > Mailing lists > Public > public-device-apis-log@w3.org > May 2021

[geolocation-api] "Living Standard" -> New Features -> Background Geolocation (#74)

From: Tom333Trinity via GitHub <sysbot+gh@w3.org>
Date: Tue, 04 May 2021 06:29:49 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-875148233-1620109788-sysbot+gh@w3.org>
Tom333Trinity has just created a new issue for https://github.com/w3c/geolocation-api:

== "Living Standard" -> New Features -> Background Geolocation ==
I am extremely enthusiastic to see recent works to resurect this spec to "Living Standard" status as confirmed [here](https://github.com/w3c/geolocation-api/issues/50#issuecomment-828930032)

Is now not the time to look to new features? 

For *5 long* years the user-base has managed to maintain the rage [in this forum](https://github.com/w3c/ServiceWorker/issues/745)

And voices in the wilderness have gone unacknowledged let alone answered in the wider [community](https://stackoverflow.com/questions/54208334/is-it-possible-to-track-geolocation-with-a-service-worker-while-pwa-is-not-open/54208989#54208989) 

Is this really not more important/urgent than how error messages are localized?

The GeoLocation sensor API has proved to be a non-starter.

The Wake-Lock API will *never* bring in CPU lock and even then it would be a grossly inefficient square peg in a round hole.

Is there nowhere that technical professionals can debate the most appropriate solution to this essential functionality?

Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/74 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 May 2021 06:29:52 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:58 UTC