Closed Bug 1267653 Opened 9 years ago Closed 8 years ago

Make an API for creating remote <xul:browser>'s running in a particular process

Categories

(Core :: DOM: Content Processes, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox49 --- affected

People

(Reporter: mconley, Assigned: mrbkap)

References

Details

(Whiteboard: btpp-backlog [e10s-multi:M1])

There are a number of cases where it's important that the parent process create a remote <xul:browser> that is running in a particular process. For example, consider Print Preview. In order to Print Preview, we first open a new tab, and then we pass in the nsIDOMWindow of the content we want to preview into that new tab's browser via the nsIWebBrowserPrint printPreview method[1]. That only works if the new tab's browser runs in the same content process as the one we're print previewing. This means that it's important for the parent to be able to create new browsers where it can ensure that the new browser can access the content of the original. So we should create an API to make this easy to do. [1]: I believe View Source is another place this is required, since nsIWebPageDescriptor's need to be shared between two browsers to ensure that we don't hit the network to view the source.
Blocks: 1165309
When are we intending to fix this, Mike?
Flags: needinfo?(mconley)
Whiteboard: btpp-followup-2016-05-05
This is something that will likely be useful once the e10s team starts focusing on multiple content processes. So, not for a little while, but probably before the end of 2016.
Flags: needinfo?(mconley)
Whiteboard: btpp-followup-2016-05-05 → btpp-backlog
Assignee: nobody → mrbkap
Whiteboard: btpp-backlog → btpp-backlog [e10s-multi:M1]
This was fixed with bug 1165309.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Blocks: 1296785
You need to log in before you can comment on or make changes to this bug.