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

Issue 652097 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 442141
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

push-up notification does not go to the tab when I clicked

Reported by k.svis...@yandex.ru, Oct 2 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1.I see push-up notification
2.I clicked in notification
3. Nothing happens

What is the expected behavior?
Transition to a tab

What went wrong?
Hasn't gone to a tab

Did this work before? No 

Chrome version: 53.0.2785.143  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

https://www.youtube.com/watch?v=WUTca0DTa1s&feature=youtu.be
Firefox work normal like this
 
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows-10 using chrome latest stable M53-53.0.2785.143 by following mentioned steps below.

1. Navigated to https://pushcrew.com/
2. Enabled location
3. Clicked on push notification
4. Observed notification at RHS corner of the browser
5. Clicked on notification
6. Observed transition is happening to different tab as expected

k.svistun@ - Are you able to reproduce this issue on incognito mode as well? Could you please recheck this issue by creating a new profile under chrome://settings with no apps or extensions in your browser. If issue still persists please provide the exact URL or sample testcase from where we can test this issue from Chrome TE end.

Thanks!
PushNotification.mp4
4.9 MB View Download
Components: -UI UI>Notifications

Comment 3 by peter@chromium.org, Oct 4 2016

Mergedinto: 442141
Status: Duplicate (was: Unconfirmed)
Thank you for the video!

You're relying on the default behaviour for non-persistent notifications, which we don't implement correctly. That's tracked in Issue 442141, so I'm marking this as a duplicate against that one.

Instead of just throwing away the object created by calling "new Notification" (your code doesn't do anything with it), consider attaching an `onclick` event listener that focuses the window, like so:

    var notification = new Notification(...);
    notification.onclick = function() {
      window.focus();
    };

That'll work around the issue until we fix it.

Sign in to add a comment