Construct LoadInfo in the parent process when using DocumentChannel
Categories
(Core :: DOM: Navigation, task, P2)
Tracking
()
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.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Depends on D64249
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D64641
Assignee | ||
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Backed out 7 changesets (bug 1617500, bug 1617789, bug 1617434) for build bustage in dom/clients/manager/ClientChannelHelper.cpp
Log:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=291144779&repo=autoland&lineNumber=28560
Push with failures:
https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&revision=1a62904bfcb7345ea90841e179e8aea5e88ffac8
Backout:
https://hg.mozilla.org/integration/autoland/rev/d9db62e5092eaeefb7049b150bdd775016c9a62d
Comment 6•5 years ago
|
||
bugherder |
Assignee | ||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
bugherder |
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Description
•