Does not work for me neither. Please fix it.

liuhao.me@ Thanks for the issue.

Tested this issue on Windows 10 and Mac OS 10.13.3 on the reported version 68.0.3440.106 and the latest Canary 70.0.3521.0 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and added the extension given in duped  issue 774983 .
2. clicked on the notification bubble and could navigate to sign in page without any issues.
Attached is the screen cast for reference.

Request you to check and confirm if anything is missed from our end in triaging the issue.
Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..

Hi,

My development team have been able to reproduce this issue on some machines whilst others appear to be unaffected. I've attached two videos, both of machines running Windows 10 + Chrome build 68.0.3440.106. In one notifications are working as normal and the other we are seeing Windows notifications pop up.

We see this occur in both chrome extensions utilising notifications and through websites.

We used the following website to quickly test other machines and roughly 4/10 are seeing Windows notifications.

https://web-push-book.gauntface.com/demos/notification-examples/

Deleted: Notifications good.mp4 354 KB

	Notifications good.mp4 354 KB View Download

Deleted: Notifications bad.mp4 279 KB

	Notifications bad.mp4 279 KB View Download

 Issue 873620  has been merged into this issue.

james.waterworth@ Thanks for the update.

Tested this issue on Windows 10 Desktop, HP-EliteBook laptop and Mac OS 10.13.3 on the reported version 68.0.3440.106 and the latest Canary 70.0.352.0 and unable to reproduce the issue as per comment #5.

Able to click on the notification bubble and no issues are observed.
Attached is the screen cast for reference.

As this issue is not reproducible at TE end, removing 'Needs-Bisect' label and requesting Platform>Extensions team to look into the issue and help in further triaging.

Thanks..

Deleted: 873428.mp4 773 KB

	873428.mp4 773 KB View Download

I sure this problem only reproducible when using windows 10 native notifications ui(black background). And you cannot reproducible with chrome notifications ui which your video has been showed.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

the problem is with Chrome extension notifications. The notifications appear (windows 10 native with black background) but clicking on them won't fire anything. It was working fine before the latest update.

Something we've noticed that may be of help. The native notifications setting in chrome://flags is set to "Default" on the machines in both of the videos I posted earlier. Wondered if this suggests that the issue is with what Chrome considers to be the "Default" notification type on each machine.

We at MightyText are also seeing this issue as well with our Chrome Extension, but only when the user is OUTSIDE OF CHROME when the notification fires in Windows 10.

If the user is in chrome when the notification fires, it works as intended.

Seeing same issue in Windows 10 - if user is in Chrome when notification triggers, the click registers fine and web page opens fine.

If user is outside of Chrome (e.g. in MS Word or something) when notification triggers, the click does nothing

We have just tested this on multiple Windows 10 machines with

Gmail desktop notifications
WhatsApp desktop notifications

clicking on these notifications is BROKEN if the user is not inside of Chrome when the notification arrives and is clicked.

This seems like a VERY bad bug for users who use other apps on their Windows machine.

Google/Chromium folks - can you not reproduce this, say, with Gmail notifications on desktop?

COnfirming that this is broken.  When I'm in another app and get a notification from Gmail , clicking a web notification in Windows 10 does NOT bring up the Chrome application automatically.  

Works fine if I get the notification when I'm in chrome already.

Hi Susan (susan.boorgula@) - two things that should help you repro:

(1) the video you shared does not have the Windows 10 Desktop Native Notifications.  This should be the default in chrome://flags starting in Chrome 68

(2) We've only been able to reproduce this when you get a notification and click on it when you AREN'T in Chrome (e.g. go to an App like Slack, Skype, etc, and get a desktop notification, then click on it)

Hi

Please refer this link to reproduce this bug.

https://firebasestorage.googleapis.com/v0/b/myfirstnodejs-8325b.appspot.com/o/notification.html?alt=media&token=7bbca5f5-d9e8-4c9f-b3bc-dcf35d13a1d3

If you click 'Notify Me' button once, then click on the notification, onclick will work.
If you click 'Notify Me' button twice continuously, then click on the notification,  onclick will not be fired. 
You can debug the code. The same procedure is working in firefox.

Hi all - thank you for the reports, there are quite a few issues in here. I'm marking this as WontFix not because there aren't issues to fix, but because it's too overloaded and it'll be hard to keep track of what's going on. More below:


  1. chrome.notifications.onClicked is not working.

This was reported and fixed with  Issue 875091 . We expect the fix to be released with Chrome 69 (~the week after next).

  2. Not everyone sees native Windows notifications.

This is expected, and we're ramping up to 100% this week. Only users on Windows 10+ Anniversary Edition (1607) onward will get native notifications.

  3. Chrome is not brought to the foreground when a notification is activated.

This might be  Issue 827924 , but I'm not sure. It'd be great if the people who run in to this could file a new issue so that we can investigate appropriately.

  4. Clicking multiple times only fires the `onclick` event once.

This is new, and I'm unable to reproduce. Thank you for making a test-case! Would you mind filing a new issue so that we can investigate appropriately?


Testing team: Thanks! Please add the UI>Notifications label to anything to do with notifications, that'll route it to our team :).

Just noticed this...

More comments on 3 (i.e., the foreground issue) as in comment #19. The has been fixed with  Issue 837796 . We expect the fix to be released with Chrome 70.