when an extension is reloaded, no disconnect event is fired on extension script message ports

Won’t fix Issue #13497881


V S.
Aug 29, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When an extension is unloaded/reloaded, its content scripts stay around (bug 13415427, also Chrome’s current behavior). While this is a design decision you can make, the behavior of message ports as currently implemented is not useful: They silently stop delivering messages and there is no disconnect event to warn the script author.

This disconnect event is, among other things, often used for detecting that content script and extension have gone out of sync and that the content script needs to be reloaded.

Having this event, or some other kind of useful behavior, would be nice.

Example code attached.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Status to “Confirmed”

  • Hello,

    Thank you for providing this information about the issue. We are best suited to test and correct broken features for future releases of MS Edge. Please feel welcome to submit your request at http://uservoice.microsoftedge.com where other developers can up-vote your suggestion.

    Best Wishes,
    The MS Edge Team

  • Microsoft Edge Team

    Changed Status from “Confirmed” to “Won’t fix”

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

Sign in