UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
The sample app is an angular 2 based app.  Please run "ng serve" and have chrome navigate to "http://localhost:4200". 

1. Make sure that browser notification permissions is set to "Ask".
2. Click on the button "Request Notification Permission"
3. Chrome should prompt the user with a popup that allows them to block or allow notifications.  Click on "x". 
4. Refresh the browser and repeat steps #2 and #3.  

What is the expected behavior?
The user closes the notification permissions popup by clicking "x". They do not choose to allow or block notifications.  If we request for permissions again we expect the popup to display again.  Is this a defect or as designed?   We suspect this is as designed but is there a workaround so that if the user closes the popup the notifications popup will be displayed again upon subsequent permission requests?   

What went wrong?
Sometimes this results in the popup being displayed and sometimes it doesn't.  However, most of the time Chrome will automatically block notifications when the user clicks on "x" to dismiss the popup.  Thus the user is never prompted again for a permissions request.  This becomes problematic in our app which requires notifications enabled to work properly. 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 

Deleted: notifier-permissions-issue.zip 55.5 KB

notifier-permissions-issue.zip 55.5 KB Download