- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Nov 2021 04:58:01 +0000
- To: public-device-apis-log@w3.org
> doesn't clarify the behavior of navigator.permissions.query() which was the heart of my question. Ah, got it... I might need to clarify ["new information about the user's intent"](https://www.w3.org/TR/permissions/#dfn-new-information-about-the-user-s-intent), which technically covers this (it just doesn't say "OS"): > ..."To **ascertain new information about the user's intent**, a user agent MAY collect information about a user's intentions. This information can come from explicit user action, aggregate behavior of both the relevant user and other users, or **implicit signals** this specification hasn't anticipated."... > I think to tie together the per-site and system-wide permission state we'd need to provide a permission query algorithm which checks the system-wide geolocation permission state. This is essentially what the recent change to Chromium does. That makes sense. The intention of the "new information about the user's intent" was to cover this case also. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/107#issuecomment-969860194 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 04:58:03 UTC