WG Revision: Geolocation #1144
Description
Specification
https://www.w3.org/TR/2025/REC-geolocation-20250818/
Explainer
https://www.w3.org/TR/geolocation/#introduction
Links
- The WG's request for this TAG review: Prepare spec as Last Call for Review of Proposed Amendments w3c/geolocation#188
- TAG review of the previous version of this specification, if any: Geolocation API #529
- A description of what has changed since our previous review: https://...#section
The following corrections were made:
- Correction: Clarify that only the emulated error code is used (#187)
- Correction: Use null instead of NaN when stationary (#173)
- Correction: Update acquisition algorithm to define data types and han…
- Correction: check for non-secure contexts (#157)
- Correction: Clarify units and reference geodetic system for latitude …
The following additions were made:
- Addition: support geolocation emulation (#183)
- Addition: Define units for accuracy (#162)
- Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPos…
The specification
- Follows the Web Platform Design Principles.
- Includes Security and Privacy Considerations sections based on answers to the Security/Privacy Questionnaire.
Where and by whom is the work is being done?
- GitHub repo: Self-Review Questionnaire for Geolocation: Security and Privacy w3c/geolocation#191
- Primary contacts:
- Marcos Cáceres (@marcoscaceres ), Apple, co-editor
- Reilly Grant (@reillyeon), Google, co-editor
- Organization/project driving the specification: it's a joint deliverable of the Devices and Sensors Working Group and the Web Applications Working Group
- This work is being funded by: W3C
- Primary standards group developing this feature: it's a joint deliverable of the Devices and Sensors Working Group and the [Web Applications Working Group]
- Incubation and standards groups that have discussed the design:
DAS WG, WebApps WG
Feedback so far
- Active horizontal reviews: Geolocation 2025-09-01 > 2025-10-02 w3c/security-request#100, Geolocation 2025-09-01 > 2025-10-02 w3cping/privacy-request#172, Geolocation 2025-09-01 > 2025-10-02 w3c/i18n-request#273, Geolocation W3C Recommendation 2025-08-18 > 2025-08-18 w3c/a11y-request#123
- Multi-stakeholder feedback: Geolocation is widely supported by all major browsers.
- Major unresolved issues with or opposition to this specification:
- Status/issue trackers for implementations:
You should also know that...
No response
Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1144