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

Issue 709212 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Long OOO (go/where-is-mgiuca)
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug
Team-Security-UX

Blocking:
issue 709230



Sign in to add a comment

Protocol handler prompt only appears once per origin.

Project Member Reported by lgar...@chromium.org, Apr 6 2017

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Visit http://permission.site/
(2) Press "Protocol Handler"
(3) Press Esc
(4) Refresh the page and try again
(5) Do the same for HTTPS

What is the expected result?
The site can prompt again?

What happens instead?
The prompt cannot appear again, and this is not surface to the user at all.

I suggest we use the same policy as the regular permission prompt embargo.

Dom, could you triage?
 
Blocking: 709230
Cc: dominickn@chromium.org benwells@chromium.org
Owner: mgiuca@chromium.org
+cc benwells, mgiuca. Assigning to the latter.

This is by explicit design. If the user ignores a protocol request from an origin, any further calls to navigator.registerProtocolHandler() are forever blocked. See ProtocolHandlerRegistry::HasIgnoredEquivalent, called from ProtocolHandlerRegistry::SilentlyHandleRegisterHandlerRequest.

Migrating this to use embargo is a possibility, but it would be pretty complicated because none of this code uses the permissions backend (just the permission requesting frontend).

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

Labels: Hotlist-EnamelAndFriendsFixIt

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

Labels: -Hotlist-EnamelAndFriendsFixIt

Sign in to add a comment