Closed Bug 1515077 Opened 2 years ago Closed 2 years ago

Extension port disconnected when a tab switched to or from the Responsive Design Mode

Categories

(WebExtensions :: General, enhancement)

enhancement
Not set
normal

Tracking

(firefox66 verified)

VERIFIED FIXED
mozilla66
Tracking Status
firefox66 --- verified

People

(Reporter: rpl, Assigned: rpl)

References

Details

Attachments

(2 files)

When a Firefox tab is switched to (or from) the Responsive Design Mode, then the extension port related to that tab is being disconnected (as in "the port API object fired the onDisconnect event").

This issue is also tracked on the "Redux DevTools Extension" github repo's issues:
- https://github.com/zalmoxisus/redux-devtools-extension/issues/421

(as a side note: the behavior mentioned in https://github.com/zalmoxisus/redux-devtools-extension/issues/421#issuecomment-441448097 is the one that Bug 1394841 fixed, but the extension is still experiencing issues on tabs switched to the Responsive Design Mode because the extension port that is connecting the extension's content script and background page is being disconnected when the tab switches back and forth the Responsive Design Mode).
Attachment #9032701 - Attachment description: Bug 1515077 - Prevent Responsive Design Mode to break extension messaging while swapping doc shells. r?zombie! → Bug 1515077 - Prevent Responsive Design Mode from breaking extension messaging while swapping doc shells. r?zombie!
Pushed by luca.greco@alcacoop.it:
https://hg.mozilla.org/integration/autoland/rev/a25969bf715e
Prevent Responsive Design Mode from breaking extension messaging while swapping doc shells. r=zombie
https://hg.mozilla.org/mozilla-central/rev/a25969bf715e
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66

Verified as fixed using steps from https://irccloud.mozilla.com/pastebin/BREb1LPT/Bug1515077_STR.md .

I will attach a postfix video.

Status: RESOLVED → VERIFIED
Attached image Postfix video
See Also: → 1301837
You need to log in before you can comment on or make changes to this bug.