Issue metadata
Sign in to add a comment
|
Notification.permission is set to blocked even after setting it to Allow on HTTP sites
Reported by
mer.dela...@gmail.com,
Nov 15 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Go to any major news sites like http://cnn.com or http://abcnews.go.com 2. Set Notification setting to "Allow". Reload the page. 3. In the console, type in Notification.permission and it will result to "denied" What is the expected behavior? Notification.permission should be reflect what's in the UI. Users should be able to set their site settings accordingly What went wrong? Notification.permission is set to "denied " even if the UI says it's set to Allow or Ask for HTTP sites. Users are unable to adjust certain site settings even with after adding sites to trusted site lists. This issue persists on multiple enterprise managed and personal machines, MAC and Windows. Did this work before? Yes 61 Does this work in other browsers? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.11.6 Flash Version:
,
Nov 15 2017
,
Nov 15 2017
Notifications is deprecated on HTTP so it will never be allowed. The fact that it can currently be toggled in Page Info is a bug. That bug should be fixed in M63 now that we've removed all default settings from Page Info. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rsesek@chromium.org
, Nov 15 2017