<geolocation> permission element

[MinhAnhL]

Hi everyone,

We would like to propose a discussion on an updated <geolocation> element, which is a revised proposal based on our initial work on the <permission> element. This new proposal inherits the motivations and most of the functionalities but has been updated following discussions with other browser vendors.

You can find the explainer documents here:

New <geolocation> explainer: https://github.com/WICG/PEPC/blob/main/geolocation_explainer.md

Original <permission> explainer: https://github.com/WICG/PEPC/blob/main/explainer.md

We believe this approach offers a more direct and declarative way to handle geolocation permissions and functionality within the HTML markup.

We invite the WebApps Working Group/DAS WG and the broader W3C community to review this proposal and provide feedback.
We are looking forward to your thoughts and discussion.

[reillyeon]

@marcoscaceres, I'd like your feedback on this proposal because it seems to me to offer an alternate solution to the difficulties we've had modernizing the getCurrentPosition() and watchPosition() functions.

[marcoscaceres]

Added for discussion at TPAC, at joint meeting with DAS. @MinhAnhL, will you be there or be able to present?

[reillyeon]

To help prepare for a discussion at TPAC do you or any of the participants in the earlier discussions of the more general PEPC proposal (e.g. @jan-ivar or @simon-friedberger) have any comments on aspects of this proposal which do not address their earlier feedback which could be addressed before the presentation?

[MinhAnhL]

Added for discussion at TPAC, at joint meeting with DAS. @MinhAnhL, will you be there or be able to present?

I'm unfortunately likely won't be able to join, but @mikewest @mharbach will be present and representing PEPC.
However, if possible I would love to get feedback prior to TPAC, I assume that there will be some questions that we can answer offline and that way it will help us to prepare a more focus discussion round at TPAC. :)

[mikewest]

Yes, I'll be at TPAC with Marian (and, happily, it doesn't look like WebAppSec intersects with DAS at all, so we should be able to make things work from a scheduling perspective).

But I agree with @MinhAnhL; it'd be ideal if we could set the conversations at TPAC up with some feedback ~now that we can iterate on. :)

[marcoscaceres]

Sounds good... for visibility, WebKit's feedback: WebKit/standards-positions#545