Closed
Bug 1202486
Opened 9 years ago
Closed 9 years ago
Small fixes for message ports
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(firefox44 fixed)
RESOLVED
FIXED
mozilla44
Tracking | Status | |
---|---|---|
firefox44 | --- | fixed |
People
(Reporter: billm, Assigned: billm)
Details
Attachments
(1 file)
9.64 KB,
patch
|
gkrizsanits
:
review+
|
Details | Diff | Splinter Review |
The message port code is a bit broken. The parameter handling in runtime.connect doesn't handle the case where the extensionId parameter is not passed in (which is the typical case). Also, the disconnect code is kind of busted. Right now we ignore disconnect messages unless the extension is listening for them. However, we need to listen for these disconnect messages so that we know not to send any messages to the other side. This patch fixes the problem.
Attachment #8657920 -
Flags: review?(gkrizsanits)
Updated•9 years ago
|
Attachment #8657920 -
Flags: review?(gkrizsanits) → review+
Comment 2•9 years ago
|
||
Backed out the whole push in https://hg.mozilla.org/integration/mozilla-inbound/rev/f2e83a8b6b8e since it was intertangled and I wasn't entirely sure which part caused Mulet mochitest-5 to become permaorange with https://treeherder.mozilla.org/logviewer.html#?job_id=14545777&repo=mozilla-inbound
Comment 4•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/cbbb1b393bd9
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox44:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla44
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•