Skip to content

Addition: support geolocation emulation - #183

Merged
reillyeon merged 18 commits into
w3c:mainfrom
sadym-chromium:sadym/geolocation-emulation
Apr 11, 2025
Merged

reillyeon merged 18 commits into
w3c:mainfrom
sadym-chromium:sadym/geolocation-emulation

Conversation

@sadym-chromium

@sadym-chromium sadym-chromium commented Mar 17, 2025 •

Copy link
Copy Markdown
Contributor

Closes #146

The following tasks have been completed:

Implementation commitment (and no objections):

Documentation (new feature):

  • [ ] Updated implementation report N/A
  • [ ] Pinged MDN N/A. will be exposed via WebDriver BiDi
  • [ ] Added example to README or spec N/A. will be exposed via WebDriver BiDi

For documentation, either create an issue or pull request in MDN's Content repo - providing as much information as you can. PR is prefered.


Preview | Diff

@jgraham

jgraham commented Mar 18, 2025

Copy link
Copy Markdown
Member

At a high level this looks right to me (i.e. I think it matches the WebDriver API in which you provide either a full set of overrides, or null).

@reillyeon

Copy link
Copy Markdown
Member

As a general comment, please add the markup to indicate that these changes are "Candidate Additions". See the existing annotations in the spec for examples.

Comment thread index.html Resolved
Comment thread index.html Resolved
@sadym-chromium sadym-chromium changed the title [WIP] feat: support geolocation emulation Mar 19, 2025
@sadym-chromium
sadym-chromium force-pushed the sadym/geolocation-emulation branch 3 times, most recently from e80cc2a to 8fc1684 Compare March 19, 2025 11:50
@sadym-chromium
sadym-chromium force-pushed the sadym/geolocation-emulation branch from 8fc1684 to d0c2e91 Compare March 19, 2025 11:51
@sadym-chromium

Copy link
Copy Markdown
Contributor Author

As a general comment, please add the markup to indicate that these changes are "Candidate Additions". See the existing annotations in the spec for examples.

done

Comment thread index.html Resolved
@sadym-chromium
sadym-chromium marked this pull request as ready for review March 19, 2025 12:17
@sadym-chromium
sadym-chromium marked this pull request as draft March 21, 2025 11:29
@sadym-chromium

Copy link
Copy Markdown
Contributor Author

Converting for draft to wait for the webdriver-bidi specification and corresponding WPT tests are landed.

@sadym-chromium
sadym-chromium marked this pull request as ready for review March 24, 2025 13:15
@sadym-chromium

Copy link
Copy Markdown
Contributor Author

Webdriver-bidi is landed.

@reillyeon

Copy link
Copy Markdown
Member

In the "implementation commitment" section above, shouldn't we still make sure that browsers are committed to implementing the new WebDriver BiDi commands?

Comment thread index.html Resolved
Comment thread index.html Resolved
sadym-chromium and others added 3 commits March 27, 2025 10:52
Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
sadym-chromium and others added 5 commits March 28, 2025 22:00
Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
Comment thread index.html Resolved
Comment thread index.html Resolved
@reillyeon

Copy link
Copy Markdown
Member

This change looks good to me, however we still need to get implementation commitment signals from browser engines. Assuming no engine has already implemented the new WebDriver BiDi commands, please file issues for each engine and update the PR template with links to them.

Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
@sadym-chromium

Copy link
Copy Markdown
Contributor Author

This change looks good to me, however we still need to get implementation commitment signals from browser engines. Assuming no engine has already implemented the new WebDriver BiDi commands, please file issues for each engine and update the PR template with links to them.

done

@reillyeon

Copy link
Copy Markdown
Member

Why is WebKit marked "N/A"?

@sadym-chromium

Copy link
Copy Markdown
Contributor Author

Why is WebKit marked "N/A"?

I'm not aware of WebKit's commitment of supporting geolocation emulation, so I marked it as N/A. I guess the proper way to signal it is just to unmark the checkbox, which I just did.

@sadym-chromium
sadym-chromium requested a review from reillyeon April 2, 2025 08:17
@reillyeon

Copy link
Copy Markdown
Member

Please file an issue against WebKit so we can get signals directly from the team. Or maybe @marcoscaceres can comment here.

@sadym-chromium

Copy link
Copy Markdown
Contributor Author

Please file an issue against WebKit so we can get signals directly from the team. Or maybe @marcoscaceres can comment here.

done

@lutien

lutien commented Apr 11, 2025

Copy link
Copy Markdown
Member

The web platform tests have been merged to WPT repo: web-platform-tests/wpt#51896 (comment).

@sadym-chromium

Copy link
Copy Markdown
Contributor Author

@reillyeon do you think we have any other blockers?

@reillyeon

reillyeon commented Apr 11, 2025 •

Copy link
Copy Markdown
Member

It looks like we have consensus from Blink and Gecko. @marcoscaceres, can you ask someone from WebKit to take a look? I'm comfortable merging this now as a candidate addition given current interest signals.

@reillyeon
reillyeon merged commit 69cc724 into w3c:main Apr 11, 2025
github-actions Bot added a commit that referenced this pull request Apr 11, 2025
SHA: 69cc724
Reason: push, by reillyeon

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants