Closed
Bug 1578393
Opened 5 years ago
Closed 5 years ago
OOP PostMessage doesn't work for docshell/test/browser/browser_browsingContext-0{2, 3}.js with fission
Categories
(Core :: DOM: Navigation, defect, P2)
Core
DOM: Navigation
Tracking
()
RESOLVED
INVALID
Fission Milestone | M4 |
People
(Reporter: farre, Assigned: farre)
References
(Blocks 1 open bug)
Details
No description provided.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → afarre
Status: NEW → ASSIGNED
Updated•5 years ago
|
Blocks: fission-mochitests
Fission Milestone: --- → M4
Comment 1•5 years ago
|
||
This is probably a combination of bug 1576407 and bug 1542415. Most of the other postMessage issues I've seen have turned out to just be window.opener
not being available on the callers, and it looks like that should affect these tests too.
Updated•5 years ago
|
Priority: -- → P2
Comment 2•5 years ago
|
||
This is invalid-ish. The tests were failing because they didn't receive cross-process postMessage events, but they weren't receiving those events because the windows sending the messages had null window.opener
values, and were therefore just failing to send the messages to their openers in the first place.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•