Disallow nested content processes

RESOLVED FIXED in mozilla16

Status

()

Core
IPC
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: Justin Lebar (not reading bugmail), Assigned: Justin Lebar (not reading bugmail))

Tracking

(Blocks: 3 bugs)

Trunk
mozilla16
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
We don't support nested content processes at the moment (bug 761935).  But Gecko will happily create them.

Until they're supported, Gecko shouldn't try to create nested content processes.

This is important because it takes us closer to being able to remove the "remote" attribute on <iframe mozbrowser>.
(Assignee)

Updated

5 years ago
Blocks: 693515
(Assignee)

Comment 1

5 years ago
Created attachment 640308 [details] [diff] [review]
Bug 772155 - Disallow nested content processes.
Attachment #640308 - Flags: review?(bzbarsky)
(Assignee)

Comment 2

5 years ago
> This is important because it takes us closer to being able to remove the "remote" attribute on 
> <iframe mozbrowser>.

In particular, an app (loaded out of process) which contains <iframe mozbrowser> will, with this patch, automagically load that mozbrowser in-process.  Which is what we want.
(Assignee)

Updated

5 years ago
Assignee: nobody → justin.lebar+bug
Comment on attachment 640308 [details] [diff] [review]
Bug 772155 - Disallow nested content processes.

r=me
Attachment #640308 - Flags: review?(bzbarsky) → review+
(Assignee)

Updated

5 years ago
Blocks: 756376
https://hg.mozilla.org/mozilla-central/rev/8e8bc0324383
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
Blocks: 1020135
You need to log in before you can comment on or make changes to this bug.