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

Issue 779340 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

window.Notification.permission returning 'denied' for http sites

Reported by u...@umerfarooq.ca, Oct 28 2017

Issue description

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

Steps to reproduce the problem:
1. Go to an http site like www.cnn.com (one that is not blocked from displaying notifications)
2. In the console check the value of window.Notification.permission
3. Repeat for an https site like https://www.cnn.com and repeat step 2

What is the expected behavior?
window.Notification.permission returns 'default' for both the http and https sites.

What went wrong?
window.Notification.permission returns 'denied' for the http site.

Did this work before? Yes 61

Does this work in other browsers? Yes

Chrome version: 62.0.3202.75  Channel: stable
OS Version: 10.0
Flash Version:
 

Comment 1 by u...@umerfarooq.ca, Oct 28 2017

Confirmed to also be happening on macOS.

Comment 2 by hdodda@chromium.org, Oct 30 2017

Cc: hdodda@chromium.org
Labels: hasbisect-per-revision Needs-Milestone OS-Linux OS-Mac
Owner: peter@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on windows 10 , ubuntu 14.04 and Mac OS 10.12.6 using chrome M62 #62.0.3202.75 and M64 #64.0.3253.0

This is regression issue broken in M62 .

Using the per-revision bisect providing the bisect results,
Good build: 62.0.3197.0(Revision: 497604).
Bad build: 62.0.3199.0 (Revision: 497962).

You are probably looking for a change made after 497673 (known good), but no later than 497674 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

 https://chromium.googlesource.com/chromium/src/+log/6c90e5bcd7448108a241823372d7b57e217da9fd..3ea904e3488e7af8b03e29fc71d9b9998ffc325b

From the CL above, assigning the issue to the concern owner 

@Peter Beverloo- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Review Url: https://chromium.googlesource.com/chromium/src/+/3ea904e3488e7af8b03e29fc71d9b9998ffc325b

Thanks!

Comment 3 by peter@chromium.org, Oct 30 2017

Status: WontFix (was: Assigned)
Correct, we removed support for the Web Notification API from insecure origins in Chrome 62. Please see the following documentation:

https://www.chromestatus.com/feature/5759967025954816
https://blog.chromium.org/2017/09/chrome-62-beta-network-quality.html
https://groups.google.com/a/chromium.org/d/topic/blink-dev/IVgkxkRNtMo/discussion

Sign in to add a comment