Closed Bug 1578393 Opened 3 months ago Closed Last month

OOP PostMessage doesn't work for docshell/test/browser/browser_browsingContext-0{2, 3}.js with fission

Categories

(Core :: DOM: Navigation, defect, P2)

defect

Tracking

()

RESOLVED INVALID
Fission Milestone M4

People

(Reporter: farre, Assigned: farre)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

No description provided.
Assignee: nobody → afarre
Status: NEW → ASSIGNED
Fission Milestone: --- → M4

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.

Depends on: 1579847
Priority: -- → P2

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: Last month
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.