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

Issue 746896 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Notification bubble is not seen on http://permission.site/

Reported by abom...@etouch.net, Jul 20 2017

Issue description

Chrome Version::61.0.3162.0 46d636d25e054da0b0d8270d525c84f39146ce30-refs/heads/master@{#488073}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.11.6,10.12.3)

What steps will reproduce the problem?
1. Launch chrome and navigate to http://permission.site/
2. Click on 'Notification' button and observe.

Actual: Notification bubble is not seen after step 2.
Expected: Notification bubble should be seen or if Notification is blocked by default then it should be shown in Page info bubble. 

This is regression issue, broken in 'M 61' and below is manual bisect:
Good build:61.0.3161.0
Bad build:61.0.3162.0

 
Actual_notification.mp4
802 KB View Download
Expected_notification.mp4
981 KB View Download
Labels: hasbisect-per-revision
Owner: peter@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Mac 10.12.5, Windows 7 & Ubuntu 14.04 using chrome Canary#61.0.3162.0.


Per revision bisect info:
------------------------

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

CHANGELOG URL
=============

https://chromium.googlesource.com/chromium/src/+log/83c49f99a4076209023e0deeb9f07a9c623f3719..393740484abb65c13ac7769ddc5a96a47befa79a

@peter: Please take a look and reassign to the right owner if it is not related to your change.

Reviewed-on: https://chromium-review.googlesource.com/558095

Thanks..!!

Comment 2 by peter@chromium.org, Jul 20 2017

Status: WontFix (was: Assigned)
We removed the ability to request notification permission from insecure origins, so this is working as intended. See the following blink-dev thread:

https://groups.google.com/a/chromium.org/d/msg/blink-dev/IVgkxkRNtMo/cXK442tLFgAJ

Sign in to add a comment