Closed
Bug 772155
Opened 12 years ago
Closed 12 years ago
Disallow nested content processes
Categories
(Core :: IPC, defect)
Core
IPC
Tracking
()
RESOLVED
FIXED
mozilla16
People
(Reporter: justin.lebar+bug, Assigned: justin.lebar+bug)
References
Details
Attachments
(1 file)
|
1.06 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
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•12 years ago
|
Blocks: browser-api
|
|
Assignee | |
Comment 1•12 years ago
|
||
Attachment #640308 -
Flags: review?(bzbarsky)
|
|
Assignee | |
Comment 2•12 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•12 years ago
|
Assignee: nobody → justin.lebar+bug
|
||
Comment 3•12 years ago
|
||
Comment on attachment 640308 [details] [diff] [review] Bug 772155 - Disallow nested content processes. r=me
Attachment #640308 -
Flags: review?(bzbarsky) → review+
|
||
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/8e8bc0324383
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
|
||
Updated•10 years ago
|
Blocks: nested-oop
You need to log in
before you can comment on or make changes to this bug.
Description
•