This may be on Facebook's end, I'll ping them. +Owen and Alex FYI

On a tangent, we switched to native notifications on Mac OS X in Chrome 59. Have you deliberately disabled those? They're not supported anymore.

Unable to reproduce this issue on Latest Canary 63.0.3233.0 by following below steps
1. Login to www.facebook.com
2. Go to settings>>Notification: Turn on
3. Open New tab page and Close the Facebook tab, now send a message from another facebook account
4. Message notifcation appears on top right corner of New tab page, click on the message notification. 
5. Its navigated to facebook page

Attaching the screencast of the same. Please let us know if we have missed any steps in the process of reproducing the issue. 

Thanks!

Deleted: Oct-5_-2017-4_48-PM.mp4 8.6 MB

	Oct-5_-2017-4_48-PM.mp4 8.6 MB View Download

Hello,

I can confirm that this issue only occurs when using non-native notifications (so doesn't affect Linux/Mac when native notifications are enabled). On Windows, as there are no native notifications, this issue is always present.

I have been able to duplicate these steps on a clean Windows machine using a fresh install of Canary and classic notifications. You can also duplicate this behaviour on Linux or Mac by disabling native notifications.

I have attached a video running a fresh install of Chrome Canary on Windows (no modifications to default config) illustrating that attempting to interact in any way with the Facebook notification fails, all that can be done is access settings or close it. However, the test notifications on the other page work fine.

I have had other people be able to reproduce this as well on Windows, or on Mac/Linux after disabling native notifications.

This functionality previously worked.

I hope that helps, and sorry for the initial confusion resulting in using non-native notifications.

Deleted: NotificationIssue.mov 12.0 MB

NotificationIssue.mov 12.0 MB Download

Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

 Issue 772716  has been merged into this issue.

oliver@ Thanks for the feeback..

Able to reproduce this issue on Windows 7 using chrome latest canary 63.0.3235.0 and stable 61.0.3163.100.

Unable to reproduce this issue on Mac OS 10.12.6 and Ubuntu 14.04 using the latest stable and Canary with the below steps.
1. Disabled the notifications in the system settings.
2. Launched Chrome and logged into facebook.
3. Clicked on the message notification when the message is received and able to navigate to facebook page.
Please find the attached screen cast for reference. Please let us know if anything is missed from our end.

This is a Non-regression issue observed only on Windows which is seen from M-50 chrome builds, Hence marking it as 'Untriaged' for further updates from Dev.

Thanks..

Deleted: 770332_Linux-Mac.webm 2.6 MB

	770332_Linux-Mac.webm 2.6 MB View Download

Although I realise it is unsupported due to the move to native notifications, by disabling native notifications on OS X, it is possible to reproduce on Mac (attached).

Deleted: Oct 9 2017 10_02 AM.webm 3.1 MB

	Oct 9 2017 10_02 AM.webm 3.1 MB View Download

I can also reproduce this issue on Canary 64.0.3249.0 MacOSX when displaying notifications from an extension 
(native notifications are enabled)

When 
  requireInteraction: true
is passed to chrome.notifications.create, the notification cannot be clicked.
When 
  requireInteraction: false
is passed, the notification closes when clicked but the onClicked callback is not triggered.



Attached simple repro extension which displays a required interaction notification when loaded, with listeners for onClicked and onClosed.

Deleted: test-notification.zip 4.1 KB

test-notification.zip 4.1 KB Download

I also observe notifications from extensions not being clickable. Is there anything else I can provide to facilitate this?

#c4, #c8 - I'm really puzzled that it reproduces on stable too, I would have expected far more reports if this is a widespread issue. I'll continue tracing the code based on recent changes.

#c7 - we indeed don't observe the Linux system setting because we have our own notification center. That's being addressed as part of a separate effort (see  Issue 676220 ).

#c11, #c10 - the issue with extension notifications where we fire onButtonClick by accident is tracked in  Issue 774983 , a fix for which is landing right now and will be merged to the Chrome 63 branch.

In reply to #c12, apologies for any confusion in my description, this doesn't reproduce on stable, only Canary. Stable works as expected.

Oli

This appears to be fixed in 64.0.3257.0

I am able to click and interact with notifications as expected

Oli

***UI Mass Triage***

As per c#14, closing this issue.If you feel this issue should still be addressed, please to reopen it or to file a new issue.