Details

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.

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.

Suggesting a root cause

Help make the web just work! Identifying a root cause helps us resolve issues more quickly. If you have a theory for the root cause or have identified and reduced a reproducible bug, include a description and any relevant code or URLs in your comment and mark it as a root cause suggestion. Our engineers will take a look and update the bug with the results of our investigation.