- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Feb 2022 11:36:51 +0000
- To: public-geolocation@w3.org
> * [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. Erm, looking at the tests they don't seem to be calling `test_driver.set_permission()` at all... If I do that locally I can get `getCurrentPosition_permission_deny.https.html` to pass, but the allow version remains stuck waiting for a position (like in `non-fully-active.https.html`'s case). -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/120#issuecomment-1046784390 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:36:53 UTC