New issue
Advanced search Search tips

Issue 916989 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Active Desktop Notifications are not replaced by subsequent notifications that reuse the same tag

Reported by a...@alibosworth.com, Dec 20

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Visit this [demo page](https://mdn.mozillademos.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API$samples/Tag_example?revision=1393671) (referenced in this [MDN article](https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API#Tag_example))
2. Allow notifications for the page
3. Click Notify Me

What is the expected behavior?
Because multiple desktop notifications are triggered in succession with the same "tag" attribute, the active notification should be replaced by each subsequent one. 

This is the behaviour in both Safari and Firefox

What went wrong?
Only the first one is shown.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 71.0.3578.98  Channel: stable
OS Version: OS X 10.14.0
Flash Version: 

From [MDN](https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API#Tag_example):

> If a notification already has the same tag and has not been displayed yet, the new notification replaces that previous notification. If the notification with the same tag has already been displayed, the previous notification is closed and the new one is displayed.

From [Google Developer Docs](https://developers.google.com/web/fundamentals/push-notifications/notification-behaviour#tag): 

>Now let's show a third notification but re-use the first tag of 'message-group-1'. Doing this will close the first notification and replace it with our new notification.
 
Components: UI>Notifications
Labels: Needs-Triage-M71
Cc: viswa.karala@chromium.org
Labels: Triaged-ET Target-73 M-73 FoundIn-71 FoundIn-73 FoundIn-72
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on chrome reported version# 71.0.3578.98 with URL provided in comment# 0 using Mac 10.14.0. As this issue is seen from M-60(60.0.3112.0), hence considering this as Non-Regression and marking it as Untriaged.
Note: Issue is not seen on Windows and Linux.

Thanks!

Owner: dewittj@chromium.org
Status: Assigned (was: Untriaged)
Giving to a notifications person.
Cc: peter@chromium.org
+Peter who knows a bit more about OSX native notifications.
It seems like updating the content of an on-screen notification in macOS is not supported. At least Firefox and even Safari resort to closing the existing notification and showing a new one.

We do the same if a notification is created with the `renotify` flag, should we just always do that instead and ignore the flag?

Comment 7 by robliao@chromium.org, Jan 17 (6 days ago)

Labels: Hotlist-DesktopUIConsider

Comment 8 by robliao@chromium.org, Jan 18 (5 days ago)

Labels: Group-Notifications

Sign in to add a comment