Closed Bug 1272342 Opened 4 years ago Closed 2 years ago

Flip the switch in AboutRedirector to make about:newtab load in the content process if e10s is enabled


(Firefox :: New Tab Page, defect, P2)




Tracking Status
e10s + ---


(Reporter: mconley, Assigned: ursula)


(Blocks 1 open bug)


All of the required work appears to be done in order to make this possible.

So let's throw the switch.
no blocking on this, but if we can get it in great.
tracking-e10s: --- → +
Priority: -- → P2
Mike, do you know why this hasn't happened? :-)
Flags: needinfo?(mconley)
(In reply to :Gijs from comment #2)
> Mike, do you know why this hasn't happened? :-)

Yes. It's a sad story.

A bunch of work was done to make the newtab work out of process, but there were a number of failing tests that were preventing her from landing it. Then Content Services (which still existed at the time), picked up the work to use as the basis for their "remotely hosted newtab page" work that they were doing.

Then that project was abandoned.

So we're in the state where we have a 9 month old patch that is probably still apply-able (modulo ESLint / small conflicts here and there), but the tests will probably still not pass.

See bug 1021654.
Depends on: 1021654
Flags: needinfo?(mconley)
I'm closing this, since Activity Stream is in the content process (woooo!!) and old about:newtab will never be.
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.