Web notifications with same tag are duplicated with multiple tabs/pages

External Issue #8782715

Details

Author
Antony R.
Created
Sep 7, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

The following snippet of code works well for a single tab/page. When it comes to multiple tabs/pages of the same site the notification is duplicated in the Action Centre for each open tab.

The specs http://www.w3.org/TR/notifications/#tags-example and https://msdn.microsoft.com/en-nz/library/mt710825 indicate that the “tag” is responsible for ensuring the same notification isn’t duplicated.

    hub.client.triggerNotification = function (title, body, url, uniqueId) {
        if (!('Notification' in window))
            return;

        Notification.requestPermission(function (permission) {
            var iconUrl = 'https://site.com/favicon.png';
            var notification = new Notification(title, { body: body, icon: iconUrl, tag: uniqueId });
            notification.onclick = function () {
                window.open(url);
            }
        });
    };

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Sebastian P.”

      Changed Assigned To from “Sebastian P.” to “Warren S.”

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Nishant N.”

      Changed Assigned To from “Nishant N.” to “Shijun S.”

      Changed Status to “External”

    • Thank you so much for reporting the issue to us! 

      This is a known limitation in our implementation at this point.  We have a coding task already in the current product cycle to implement support to the tag property.  We are resolving the issue as a duplicate to the internal coding task, and will provide update when we have the fix ready (and to close the issue). 

      All the Best, MS Edge Team

    • This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.

    You need to sign in to your Microsoft account to add a comment.

    Sign in