1513045 - [meta] Enable privileged content process for about:home by default and let it ride the trains

Status: RESOLVED FIXED

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

Description

[Mike Conley (:mconley) (:⚙️)]

Bug 1472212 landed the foundational code and enabled the privileged content process on Nightly. This bug will track the work required to get it riding the trains out to release.

Comment 1

[Nika Layzell [:nika] (ni? for response)]

Hey :mconley - what's the status of this & do we have an assignee?

Comment 2

[Mike Conley (:mconley) (:⚙️)]

(In reply to :Nika Layzell from comment #1)

Hey :mconley - what's the status of this & do we have an assignee?

Bug 1509250 is the last bug that I know of blocking this work. I had a patch for that1, but it was failing some tests and I never got back around to finishing it off. I think part of the problem was that if a new window was being opened at some URI X, my patch made us do a process flip, when what we should have done was plumb the URI X through to the chunk of the browser code that sets the initial tab's process type, and make sure it chooses the right one.

Is this blocking you?

Comment 3

[Nika Layzell [:nika] (ni? for response)]

Nope, it's just currently marked for fission-M2, so I wanted to know if progress was being made on it :-)

Comment 4

[Chris Peterson [:cpeterson]]

M6 because privileged content process doesn't block dogfooding. Blocked waiting for DocumentChannel.

Comment 5

[Chris Peterson [:cpeterson]]

mconley, can we close this meta bug as fixed? All the blocking bugs are fixed.

Comment 6

[Mike Conley (:mconley) (:⚙️)]

I was planning on closing this one out as soon as the privileged about content process transitioned to the release channel. Is that okay?

Comment 7

[Mike Conley (:mconley) (:⚙️)]

This has gone out to release. We're done here.