- From: Tom333Trinity via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 May 2021 02:08:35 +0000
- To: public-geolocation@w3.org
Please explain why you insist on cancelling active discussion of this feature. Where is the harm? [WICG](https://discourse.wicg.io/t/proposal-geolocation-sensor-based-on-the-generic-sensor-api/2355) has dead-ended on this topic with a redundant API deferring any novelle functionality to a mythical version 2+ It was declared out-of-scope for the Geolocation Sensor API because that API is simply incapable of supporting Background Geolocation. So what is stopping it becoming in scope here? Or it's own spec if that is more appropriate? For 5 years you have been playing wack-a-mole with any mention of background geolocation in the face of huge demand from the client-base and web developers in particular. How can W3C have achieved nothing in this area over 5 years yet still insist on stifling/cancelling debate? -- GitHub Notification of comment by Tom333Trinity Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/74#issuecomment-832367471 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 May 2021 02:08:39 UTC