Re: [geolocation-api] Investigate test failures to exit CR (#120)

Looking at, I see 3 tests failing:

* [getCurrentPosition_permission_deny.https.html]( and [getCurrentPosition_permission_allow.https.html]( 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]( is failing because of 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 using your GitHub account

Sent via github-notify-ml as configured in

Received on Monday, 21 February 2022 11:08:04 UTC