Notification API does not pass cookies to icon request

Fixed, not yet flighted Issue #8436807


Aug 9, 2016
This issue is public.
Found in
  • Microsoft Edge
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

We have Web application, that passes to server SESSION_ID in cookies.
Using MS Edge Notification API it is unable to show icons, which require authenticated user session.
Those icons are shown fine in other browsers: Chrome, FF.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • Would you be able to provide us with the extension itself that you are reporting this against so that we can look into this in detail?

      If not do you think you could provide the extension itself, please provide a code sample.

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • I do not think this is about an extension, just the Notification API.

      Let’s say that our server serves the image of the current logged in user (with correct mime and everything) through the URL. Our server requires that the current user is authenticated in order to retrieve and serve the photo.

      Edge does not use the authentication cookies for the domain when requesting the notification icon from and thus no photo can be fixed.
      Since this is a request to a domain, Edge should include all cookies to that domain when requesting an icon for a notification, as for example, like any XHR request.
      Other browsers already follow this behaviour.

    • Microsoft Edge Team

      Changed Status from “Not reproducible”

    • I see. Thanks for clarifying. Reactivating for review.

    • Microsoft Edge Team

      Changed Assigned To to “Sermet I.”

      Changed Title from “Notification API does not pass cokies to icon request” to “Notification API does not pass cookies to icon request”

      Changed Assigned To to “Venkat K.”

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

      Changed Assigned To from “Nishant N.” to “Brad E.”

      Changed Status to “Fixed, not yet flighted”

    • We have the fix checked into our internal builds at this time. We are working on including this functionality in our insider preview builds and then ultimately to the public as soon as possible.

      Best regards,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status from “Fixed, not yet flighted” to “Fixed, flighted”

      Changed Status from “Fixed, flighted” to “Fixed, not yet flighted”

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

    Sign in