- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jul 2020 15:25:13 +0000
- To: public-geolocation@w3.org
As @marcoscaceres rightly points out, new feature proposals beyond editorial text tweaking are out of scope for the Geolocation API since this spec is in maintenance mode. Maintenance includes hardening this quite old API for privacy and security to the extend we can without breaking existing content. For new feature discussion, there's another API called [Geolocation Sensor](https://w3c.github.io/geolocation-sensor/). Please see its issues labeled [geo-accuracy](https://github.com/w3c/geolocation-sensor/issues?q=label%3Ageo-accuracy+) and submit this feedback there. See also [all open issues](https://github.com/w3c/geolocation-sensor/issues). Related, and probably of interest to @pes10k as well: Feedback is also welcome on the [new use cases](https://w3c.github.io/geolocation-sensor/#use-cases) that motivate every new geolocation feature under consideration. Out of these use cases, especially the background operations are highly demanded by web developers but at the same time they are also the most tough ones to solve in a privacy-preserving manner and thus have not advanced beyond use case solicitation at this point. We're hopeful we'll get there eventually, but we don't yet know what API shape and form will get us there. We think, however, that retrofitting the Geolocation API with new features for use cases such as background operation is not a viable option due to its aging design. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/49#issuecomment-652485416 using your GitHub account
Received on Wednesday, 1 July 2020 15:25:15 UTC