design-reviews#1140: Incubation: `<geolocation>` element (part of PEPC)

#1140: Incubation: `<geolocation>` element (part of PEPC)

Visit on Github.

Opened

Aug 20, 2025

Explainer

https://github.com/WICG/PEPC/blob/main/geolocation_explainer.md, https://github.com/WICG/PEPC/blob/main/explainer.md

The explainer

Includes the information requested by the Explainer Explainer.
Follows the Web Platform Design Principles.
Includes or links to answers to the Security/Privacy Questionnaire.
Describes user research you did to validate the problem and/or design.

Where and by whom is the work is being done?

GitHub repo: https://github.com/WICG/PEPC
Primary contacts:
- Alexandru Paicu (@andypaicu), Google Chrome, Implementor
- Daniel Vogelheim (@otherdaniel), Google Chrome, Spec Editor
Organization/project driving the design: Google Chrome
This work is being funded by: Google Chrome
Incubation and standards groups that have discussed the design:
- https://github.com/WICG/PEPC/issues/59
Standards group(s) that you expect to discuss and/or adopt this work when it's ready: unknown

Feedback so far

Multi-stakeholder feedback:
- Chromium comments: This feature allows for significant improvements for the user experience which would not be feasible otherwise.
- Mozilla comments: https://github.com/mozilla/standards-positions/issues/1245, https://github.com/mozilla/standards-positions/issues/1288 (only raised today, might not have any feedback yet), https://github.com/WICG/PEPC/issues/59
- WebKit comments: none specifically for the <geolocation> element.
- {{...include feedback/review from developers, implementers, civil society, and others}}

You should also know that...

Important note: this is part of "permission" element proposal (https://github.com/w3ctag/design-reviews/issues/1079). Based on various discussions and feedback, we're proposing a split from a one-size-fits-all element to elements focused on specific capabilities. This is the proposal for a <geolocation> element. This element would inherit from the <permission> element all of its attributes, events, and checks. In the end the <permission> element would serve as a base class for the various capability-focused elements, and would no longer be usable directly.