- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Feb 2022 11:08:02 +0000
- To: public-geolocation@w3.org
Looking at https://wpt.fyi/results/geolocation-API?label=experimental&label=master&aligned, I see 3 tests failing: * [getCurrentPosition_permission_deny.https.html](https://wpt.fyi/results/geolocation-API/getCurrentPosition_permission_deny.https.html?label=experimental&label=master&aligned) and [getCurrentPosition_permission_allow.https.html](https://wpt.fyi/results/geolocation-API/getCurrentPosition_permission_allow.https.html?label=experimental&label=master&aligned) are failing because even though `test_driver.set_permission()` is being called, the `chrome` binary is still prompting for geolocation access instead of granting/denying requests. It's probably a good idea to file a bug for this if there isn't one already. * [non-fully-active.https.html](https://wpt.fyi/results/geolocation-API/non-fully-active.https.html?label=experimental&label=master&aligned) is failing because of https://bugs.chromium.org/p/chromium/issues/detail?id=1233329. I've done some quick hacking to fix that bug locally but the test is still timing out -- I'm guessing there's nothing providing geolocation data so the final call to `getCurrentPosition()` never resolves or rejects. -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/120#issuecomment-1046757858 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 February 2022 11:08:04 UTC