Confusion about geolocation emulation in two specs

[marcoscaceres]

Web Driver spec has:
https://www.w3.org/TR/webdriver-bidi/#command-emulation-setGeolocationOverride

Our spec has:
https://www.w3.org/TR/geolocation/#emulation

Shouldn't we own the emulation for geolocation?

@reillyeon, as I wasn't part of the discussion for adding the emulation stuff to the spec, did you talk about that? What (if anything) should be done here?

[sadym-chromium]

There are 2 approaches on WebDriver BiDi specification: having the command definition in the main spec and invoke hooks on the external (external to the WebDriver BiDi spec) specification (Geolocation is done this way), or defining the WebDriver BiDi commands completely in the external specification (like permissions or web bluetooth).

There was a related discussion on TPAC 2024. The main driver for keep the command in the main WebDriver BiDi spec is the complications in generating commands definitions. It is not a blocker, but slightly easies our lives.

I don't think we have objections on moving the command definition to the geolocation spec if you have strong arguments for that, but these would reduce the visibility of potential future changes, and as a result, a potential increased latency in implementation.

[reillyeon]

+1 to what @sadym-chromium said. I don't have a strong opinion either way.

[reillyeon]

Discussed at TPAC 2025. Resolved to keep the split and add a non-normative reference from Geolocation to WebDriver for the automation section.