New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 751857 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature
Team-Security-UX



Sign in to add a comment

Make permissions.query return the value that reflects whether the current context can prompt for/use permission

Project Member Reported by raymes@chromium.org, Aug 2 2017

Issue description

Currently the API in Chrome just returns whether a top-level window can prompt for/use permission. This is useful in some specific circumstances (e.g. for notification requests that happen in popups). But it's more consistent to return the result for the current context. 

Action items:
1) Decide whether to make an explicit exception for workers/worklets/SWs; if not, then update them to always return "denied" instead of "prompt" for all permissions that require prompting.
2) Update Permissions API spec to clarify this.
3) Update Notifications spec to refer to Permissions API spec for getting permission state.
4) Update Notification::permission & NotificationPermissionContext::DecidePermission to return "denied" instead of "prompt" in iframes (ditto for any similar permissions?).
5) Gather developer feedback on whether we need a new API to predict permission state in new popups.
 
Cc: dominickn@chromium.org
raymes@ what's the goal of this change?
Cc: mlamouri@chromium.org

Comment 4 by raymes@chromium.org, Aug 30 2017

See the thread here: g/chrome-permissions-team/eTLqU9H0K8A from which the AIs are copied.

Comment 5 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt

Comment 6 by est...@chromium.org, Feb 18 2018

Labels: -Hotlist-EnamelAndFriendsFixIt
Labels: -Type-Bug Type-Feature
This looks to me like a feature request as it's an improvement proposal of the current API rather than fixing a bug in the current API.

Sign in to add a comment