- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Nov 2021 00:10:35 +0000
- To: public-device-apis-log@w3.org
Your PR clarifies the behavior of getCurrentPosition() and watchPosition(). That's a good thing to do but doesn't clarify the behavior of navigator.permissions.query() which was the heart of my question. I think to tie together the per-site and system-wide permission state we'd need to provide a [permission query algorithm](https://www.w3.org/TR/permissions/#dfn-permission-query-algorithm) which checks the system-wide geolocation permission state. This is essentially what the recent change to Chromium does. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/107#issuecomment-969476728 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 November 2021 00:10:37 UTC