Closed Bug 1316748 Opened 8 years ago Closed 5 years ago

Move WebExtension Port messaging off MessageChannel

Categories

(WebExtensions :: General, defect, P1)

51 Branch
defect

Tracking

(firefox76 fixed)

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: aswan, Assigned: zombie)

References

(Blocks 1 open bug)

Details

(Whiteboard: triaged)

Attachments

(1 file, 1 obsolete file)

Follow-up from https://bugzilla.mozilla.org/show_bug.cgi?id=1313980#c21 Kris may want to expand on this but I think it makes sense to continue to use MessageChannel for setting up and tearing down Ports but to use message managers directly for postMessage, avoiding the extra filtering/routing in MessageChannel.
See Also: → 1313980
Priority: -- → P3
Whiteboard: triaged
still relevant?
Flags: needinfo?(aswan)
Probably not, I understand Kris has plans in this area but I don't know what they are.
Flags: needinfo?(aswan) → needinfo?(kmaglione+bmo)
Product: Toolkit → WebExtensions
Flags: needinfo?(kmaglione+bmo)

Some of the linked comments are probably relevant for the coming rewrite related to fission, marking as blocking to remember to look into it later.

Blocks: 1583484

This should in theory be least dependent on bug 1580448, as the perf impact of sending individual messages to listeners in multiple iframes (instead of broadcasting via MessageManagers) will be localized only to the connect call, while most individual port messages are going to be 1:1 in the common case.

Assignee: nobody → tomica
Priority: P3 → P1
Attachment #9134105 - Attachment is obsolete: true
Pushed by tjovanovic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/601e0a6a8ee9 Move Port messaging off MessageChannel r=mixedpuppy
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Regressions: 1624124
Regressions: 1624235
Regressions: 1635637
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: