This bug is caused by `runtime.onConnect` unexpectedly triggering in the browser action popup panel. This should not happen, the `runtime.onConnect` event should not be triggered when the event is registered in the same location as `runtime.connect`. We will fix this, but meanwhile extensions can try to work around this by ignoring unexpected `onConnect` calls. In the Amazon extension, this could be done by returning early from `_panelConnectHandler` when `_panelPort` has been set before (by `createConnectionToExtension`)
Bug 1635637 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug is caused by `runtime.onConnect` unexpectedly triggering in the browser action popup panel. (EDIT: not just browser action popups but any other extension page, such as extension tabs and background pages). This should not happen, the `runtime.onConnect` event should not be triggered when the event is registered in the same location as `runtime.connect`. We will fix this, but meanwhile extensions can try to work around this by ignoring unexpected `onConnect` calls. In the Amazon extension, this could be done by returning early from `_panelConnectHandler` when `_panelPort` has been set before (by `createConnectionToExtension`)