- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Oct 2021 21:59:12 +0000
- To: public-device-apis-log@w3.org
reillyeon has just created a new issue for https://github.com/w3c/geolocation-api: == Specify behavior for operating system permissions == Implementations of the Geolocation API on some operating systems need to themselves request permission to access device location. The specification does not currently say what happens if the user grants a site permission to use the "geolocation" feature in [check permission](https://w3c.github.io/geolocation-api/#dfn-check-permission) but the operating system denies access to the device location in [acquire position](https://w3c.github.io/geolocation-api/#dfn-acquire-position). In Chromium we recently implemented a change in [issue 1200933](https://crbug.com/1200933) which synchronizes the per-site and system-wide permission state as exposed through the Permissions API. In [issue 1246955](https://crbug.com/1246955) a developer noted that this new behavior is not consistent with Firefox. Note, Safari does not implement the navigator.permissions.query() method however it is still possible to observe the difference because (at least in my testing) the GeolocationPositionError.message field is initialized differently when Safari itself does not have permission to use location. The current behavior in Firefox and Safari does not seem intentional however it is clearly useful to at least one developer. The Chromium project is open to either its current or previous behavior as long as this specification is clear on which is expected. Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/107 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 October 2021 21:59:14 UTC