Closed
Bug 1602320
Opened 5 years ago
Closed 3 years ago
Reduce the number of parameters needed to create DocumentChannel/DocumentLoadListener
Categories
(Core :: Networking, task, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
People
(Reporter: mattwoodrow, Unassigned)
References
Details
(Whiteboard: [necko-triaged])
We currently pass an nsDocShellLoadState in DocumentChannelCreationArgs, but we also pass a lot of other state coming from the originating docshell.
In order to do DocumentChannel creation from the parent-process (bug 1602318), we'll need to be able to do this without reading from any docshell, but we should have a BrowsingContext instead.
I think most of these values fall under one (or more) of a few categories)
- Things that are computed from the nsDocShellLoadState, and need that computation code factored out of docshell.
** LoadInfo is mostly this, thought some sub-components may fall under other categories - Things that are available from the BrowsingContext, or should be.
** initiatorType, isActive, isTopLevelDoc, hasNonEmptySandboxingFlags - Things that could just be statically known
** If we current do a process-switch before starting a top-level load, then we'd get a brand new docshell, so some values will be guaranteed to be their default value in this case. - Things that could be computed in the parent
** Async open time, channel id
Updated•5 years ago
|
Priority: -- → P2
Whiteboard: [necko-triaged]
Comment 1•3 years ago
|
||
Hi Nika, it looks like this bug is already done. Can we close this one?
Thanks.
Flags: needinfo?(nika)
Comment 2•3 years ago
|
||
resolving as fixed
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(nika)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•