Closed Bug 1617500 Opened 5 years ago Closed 4 years ago

Construct LoadInfo in the parent process when using DocumentChannel

Categories

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

task

Tracking

()

RESOLVED FIXED

People

(Reporter: mattwoodrow, Assigned: mattwoodrow)

References

Details

Attachments

(2 files)

Bug 1602318 wants to construct DocumentLoadListener directly in the parent process without a content process.

To do so, we need to be able to construct all necessary arguments using data we have in the parent.

Ideally we'll construct the LoadInfo in the parent, even for content initiated loads, so that both sources take the same code path.

This will also help with an existing bug with OOP <iframes>, where we try to construct the LoadInfo in the content process, but can't do so properly without access to our ancestors.

See Also: → 1617502
Depends on: 1617789
Assignee: nobody → matt.woodrow
Pushed by mwoodrow@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1a62904bfcb7 Create top-level document LoadInfo directly in parent process with DocumentChannel. r=nika
Keywords: leave-open
Pushed by mwoodrow@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/13837165109d Create top-level document LoadInfo directly in parent process with DocumentChannel. r=nika
Flags: needinfo?(matt.woodrow)
Pushed by mwoodrow@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0224dccf2bb5 Don't try to compute ancestors for a top-level window in the LoadInfo constructor. r=nika,ckerschb
Status: NEW → ASSIGNED
Priority: -- → P2
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: