Open Bug 1648369 Opened 4 years ago Updated 4 years ago

Replace BrowsingContext::InternalLoad with BrowsingContextL::LoadURI.

Categories

(Core :: DOM: Navigation, enhancement, P3)

Product:
Core
Component:
DOM: Navigation
Type:
enhancement

Tracking

()

Project Flags:
Fission Milestone Future

People

(Reporter: farre, Unassigned)

References

Details

WindowGlobalParent::RecvInternalLoad basically only redirects the internal load to the content child that contains the in-process browsing context. This in turn will result in a round trip that eventually ends up in the parent process to initiate the DocumentLoadListener. Short-circuting that would be good.

Severity: -- → S3
Type: defect → enhancement
Priority: -- → P3

@ Andreas, is this bug for follow-up work from a code review? If so, which bug was that?

Is there an existing bug to handle loads in the parent process?

Fission Milestone: --- → Future
Flags: needinfo?(afarre)
Flags: needinfo?(afarre)
See Also: → 1645781, 1590782

I guess the parent controlled load bug is bug 1647557.

See Also: → 1647557

Andreas, do you know why we need BrowsingContext to have both InternalLoad and LoadURI?

If we could combine those two, then we'd get the speculative-load from parent that's already in-tree, as well as the new code from bug 1647557.

Flags: needinfo?(afarre)

Yes, combining InternalLoad and LoadURI would be great. This bug should do that, I'll update the description.

Flags: needinfo?(afarre)
Summary: Try to handle more of BrowsingContext::InternalLoad re-targeting in the parent process. → Replace BrowsingContext::InternalLoad with BrowsingContextL::LoadURI.
You need to log in before you can comment on or make changes to this bug.