[w3ctag/design-reviews] WG Revision: Geolocation (Issue #1144)

siusin created an issue (w3ctag/design-reviews#1144)

### 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: https://github.com/w3c/geolocation/issues/188
- TAG review of the previous version of this specification, if any: https://github.com/w3ctag/design-reviews/issues/529
- A description of what has changed since our previous review: https://...#section

[Correction: Clarify that only the emulated error code is used](https://github.com/w3c/geolocation/commit/0cc35fa) ([#187](https://github.com/w3c/geolocation/pull/187))
[Addition: support geolocation emulation](https://github.com/w3c/geolocation/commit/69cc724) ([#183](https://github.com/w3c/geolocation/pull/183))
[Correction: Use null instead of NaN when stationary](https://github.com/w3c/geolocation/commit/9d5829e) ([#173](https://github.com/w3c/geolocation/pull/173))
[Correction: Update acquisition algorithm to define data types and han…](https://github.com/w3c/geolocation/commit/22ed7a4)
[Addition: Define units for accuracy](https://github.com/w3c/geolocation/commit/a30d713) ([#162](https://github.com/w3c/geolocation/pull/162))
[Correction: check for non-secure contexts](https://github.com/w3c/geolocation/commit/c2fdd74) ([#157](https://github.com/w3c/geolocation/pull/157))
[Addition: expose .toJSON() on GeolocationCoordinates + GeolocationPos…](https://github.com/w3c/geolocation/commit/09b48e6)
[Correction: Clarify units and reference geodetic system for latitude …](https://github.com/w3c/geolocation/commit/74b1dd0)


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/w3c/geolocation/issues/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](https://www.w3.org/groups/wg/das) and the [Web Applications Working Group](https://www.w3.org/groups/wg/webapps)
- 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](https://www.w3.org/groups/wg/das) 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: https://github.com/w3c/security-request/issues/100, https://github.com/w3cping/privacy-request/issues/172, https://github.com/w3c/i18n-request/issues/273, https://github.com/w3c/a11y-request/issues/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_

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1144


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1144
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1144@github.com>