You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If multiple notifications are read during a short timespan, such as if there are multiple tabs open for a site that sends desktop notifications, all of these notifications are displayed at once, and logged in the history pane.
It would be good practice to do some intelligent sensing of these duplicates, and make a decision as to whether any given incoming notification is valid before presenting it to the user. Items with identical image, title and body (perhaps also received within the last second or so) ought to be discarded.
The text was updated successfully, but these errors were encountered:
Do you have a more concrete example of what you mean by duplicates in this case? If we're getting duplicates in the notification center, it's a bug and it would be good to know how to reproduce that. If you're instead suggesting we introduce some logic to gauge how likely it is two notifications from the same application are "to be connected" or that somehow one should be discarded, this is a feature request.
In the latter case, however, I find the word "duplicate" misleading, as the notifications would indeed be different.
If multiple notifications are read during a short timespan, such as if there are multiple tabs open for a site that sends desktop notifications, all of these notifications are displayed at once, and logged in the history pane.
It would be good practice to do some intelligent sensing of these duplicates, and make a decision as to whether any given incoming notification is valid before presenting it to the user. Items with identical image, title and body (perhaps also received within the last second or so) ought to be discarded.
The text was updated successfully, but these errors were encountered: