New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 898536 link

Starred by 7 users

Issue metadata

Status: Available
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

Support for geotracking

Project Member Reported by tsteiner@google.com, Oct 24

Issue description

Feature description: Geotracking allows apps to track the location of the user (upon approval) in the background while not using the app. This allows for things like turn-by-turn navigation.

Eng owner: tbd
Product owner: nattestad@

Design doc: https://w3c.github.io/geolocation-sensor/
 
Cc: anssi.ko...@gmail.com
Status: Available (was: Assigned)
marking as available as we still need to search an eng for implementation of this.
Please explain why Geolocation is considered to be another sensor? When will a foreground user opt for this API over the existing navigator.geolocation.*?

More importantly, why do you refuse to implement the battery friendly, feature rich ServiceWorker.TravelManager that was proven here: - https://github.com/RichardMaher/Brotkrumen

Let's not forget on how much money and effort chrome developers wasted on "implementing" the geofencing API!

Sign in to add a comment