-
Notifications
You must be signed in to change notification settings - Fork 21
Issues: w3c/geolocation-sensor
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Missing tasks in parallel steps in Geolocation Sensor
#63
opened Sep 9, 2024 by
dontcallmedom-bot
1 task
What are the current and planeed Implementations of the Geolocation Sensor API
question
#44
opened May 5, 2021 by
Tom333Trinity
The [Constructor] extended attribute (on GeolocationSensor) is deprecated
#41
opened Mar 20, 2020 by
xfq
Background geolocation and user privacy issues
geo-background-tracking
privacy-tracker
Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
#39
opened Jun 16, 2019 by
FluorescentHallucinogen
Revisit GeolocationSensor.Accuracy and Latency
geo-accuracy
geo-latency
#25
opened Aug 9, 2018 by
gmandyam
Sensor.frequency needs to be setable to allow frequency adaptation
geo-update-frequency
#16
opened Feb 21, 2018 by
anssiko
Notification that the requested accuracy is not available
geo-accuracy
#15
opened Feb 19, 2018 by
blairmacintyre
Trigger readings only upon geolocation change instead of time interval
geo-foreground-tracking
#13
opened Feb 6, 2018 by
martijnthe
Allow page to provide hints as to data saver/power consumption mode
geo-power-saver
#3
opened Oct 5, 2017 by
markafoltz
Developer-set constraints on latency/accuracy of initial reading
geo-accuracy
geo-latency
#2
opened Oct 5, 2017 by
markafoltz
ProTip!
Follow long discussions with comments:>50.