Open Bug 1376894 Opened 2 years ago Updated 2 years ago

Support a special attribute on <xul:browser>'s that cause the next page load to use a preallocated process

Categories

(Core :: DOM: Content Processes, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: mconley, Assigned: gkrizsanits)

References

Details

(Whiteboard: e10s-multi:+)

We want the preloaded about:newtab page to only use a preallocated process once it has navigated somewhere (until then, it should use a pre-existing content process).

gabor suggested that we decorate the preloaded about:newtab page with a special attribute, and then have nsFrameLoader/ContentParent do some sleight-of-hand to switch the process that the content is loading in to the next preallocated content process (if a preallocated content process is available).
Hey gabor, can we just assign this to you?
Flags: needinfo?(gkrizsanits)
Assignee: nobody → gkrizsanits
Flags: needinfo?(gkrizsanits)
Blocks: 1381804
Priority: -- → P3
Summary: Support a special attribute on <xul:browser>'s that cause the next page load to use the preallocated process → Support a special attribute on <xul:browser>'s that cause the next page load to use a preallocated process
Whiteboard: e10s-multi:+
You need to log in before you can comment on or make changes to this bug.