Re: Request to obsolete Geolocation Sensor

Right, Geofencing is not specifically tied to the Geolocation Sensor spec - nor really part of it at all. It could (and absolutely should) be done as an enhancement of the existing Geolocation API. 

We could make another attempt at incubating something. The challenge last time was certain individual(s) ruining it by persistent trolling (to the point where no one wanted to work on it 😿), so hopefully we can find a way of working without it getting derailed again and again… and again. 😔 

At the same time, as we well know, there’s a lot of user privacy and OS integration challenges. But we have potentially somewhat better models nowadays to deal with that. 
 

> On 17 May 2024, at 10:59, Thomas Steiner <tomac@google.com> wrote:
> 
> 
>> There is still clear developer interest in some kind of geofencing capability however that would likely be a different specification which could coexist with the Geolocation API.
> 
> Geofencing and background geolocation. See https://github.com/w3c/geolocation-sensor/issues/22 specifically.