W3C home > Mailing lists > Public > public-device-apis-log@w3.org > March 2022

Re: [geolocation-api] Transition to Proposed Recommendation (#121)

From: Reilly Grant via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Mar 2022 21:59:25 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-1062258572-1646776764-sysbot+gh@w3.org>
On the Chromium side I'm taking a look at our internal test runners to make sure the tests Marcos added to WPT are working even if the WebDriver stuff is broken (internal Chromium tests don't use WebDriver). Chromium also has internal tests which use a more advanced test-only API to exercise API behavior: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/wpt_internal/geolocation-api/

So, even with the existing WebDriver API for permissions control fixed we probably still need to expose WebDriver's [setGeoLocation](http://v4.webdriver.io/api/mobile/setGeoLocation.html) method through the test_driver API so that when run in automation these tests can actually provide location in a reliable way.

GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/121#issuecomment-1062258572 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 March 2022 21:59:27 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:59 UTC