New issue
Advanced search Search tips

Issue 735866 link

Starred by 1 user
Status: Duplicate
Merged: issue 729171
Owner: ----
Closed: Jun 2017
Cc:
dominickn@chromium.org
emilyschechter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

Temporarily blocking permission can't be reset.

Reported by adam.gar...@gmail.com, Jun 22 2017 
Chrome Version       : 59.0.3071.104 (Official Build) (64-bit)
URLs (if applicable) : https://jsfiddle.net/yoshi6jp/Umc9A/
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: N/A
    Firefox: N/A
         IE: N/A

What steps will reproduce the problem?
(1) Click on "Request Permission"
(2) Ignore the prompt by clicking close.
(3) Repeat Step 1 & 2 twice.
(4) Chrome blocks the permission request prompt silently.

What is the expected result?
Based on the instruction on Chrome Status page (https://www.chromestatus.com/feature/6443143280984064), changing permission setting on page info dialog can reset the status to non-blocked. 


What happens instead?
Changing permission settings does not work.


Please provide any additional information below. Attach a screenshot if
possible.
If you type `Notification.requestPermission()` in console three times, the instruction works but not in the case when service worker involved.
permission.png
46.2 KB View Download

Comment 1 by dominickn@chromium.org, Jun 22 2017

Mergedinto: 729171
Status: Duplicate (was: Unconfirmed)
Thanks for the report.,

This occurs because JSFiddle embeds a cross-origin iframe that is actually doing the requesting. You will note that in the permission prompt, it says that the origin requesting is "fiddle.jshell.net", which is not "jsfiddle.net". Hence, using the page info dialog to reset permission doesn't work because the page info dialog refers to the top level origin (jsfiddle.net), while the origin that's embargo is "fiddle.jshell.net". To reset the embargo, you will need to clear your browsing data.

We have some plans to make this more user-friendly. However, as an aside, requesting notifications permission from an iframe is going to be removed as of Chrome 61, so you won't be able to request permission at all in this instance soon (and hence it won't be embargoable).

Comment 2 Deleted

Comment 3 by adam.gar...@gmail.com, Jun 23 2017 

No matter the origin is subdomain or not, it's still unable to reset the status of being blocked.

You may try another demo, for example, https://gauntface.github.io/simple-push-demo/

Comment 4 by dominickn@chromium.org, Jun 23 2017 

That site works fine for me: I push the toggle and dismiss the prompt 3 times. The prompt is automatically blocked, I open up the page info dialog, reset it to Ask, and then the prompt works again.

Comment 5 by adam.gar...@gmail.com, Jun 23 2017 

That's weird. The page I'm working on won't show "automatically blocked" while pushManager is request for permission for the 4th time. Well, maybe it's my bug.
►

Sign in to add a comment