UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome and visit https://jsbin.com/mayamamohi/edit?html,js,output
2. Open the Console from developer tools
3. Hit Request Permission, and press Escape to close the bubble
4. Observe that the Request Permission button remains disabled implying that the `Notification.requestPermission()` Promise has not resolved yet, but the bubble disappears. There is nothing logged to the console.
5. Switch to a new tab and back. Observe that the bubble is visible again.

Video: https://cldup.com/7Hf3YL97Xs.gif

What is the expected behavior?
Expected behavior is the same as how the 'x' button press behaves:

1. Launch Chrome and visit https://jsbin.com/mayamamohi/edit?html,js,output
2. Open the Console from developer tools
3. Hit Request Permission. Observe that the Request Permission button get disabled.
4. Click on the 'x' to close the bubble. Observe that the 'The permission request was dismissed.' line is logged to the console. The Request Permission button is enabled again.

What went wrong?
Hitting Escape to close the permission bubble leaves the UI in a broken state, and after switching to a new tab and back the permission bubble is visible again so Escape does not fully close it.

Some sites that use notifications and are broken because of this issue:

Facebook: https://cloudup.com/ieFDscA85jz
Googe Drive: https://cloudup.com/iCwx7E4lfAx
Twitter: https://cloudup.com/iKpnNuevOlW
WordPress.com: https://cloudup.com/iIyXko7l8Pl

Did this work before? Yes Chrome 50 still worked as expected, Chrome 51 and up (until 54 at the moment) does not work anymore.

Chrome version: 52.0.2743.116  Channel: stable
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0
 

Deleted: test_source.zip 836 bytes

test_source.zip 836 bytes Download