Closed
Bug 1186296
Opened 9 years ago
Closed 9 years ago
Manage nsIBrowserElementAPI in TabParent
Categories
(Core :: DOM: Core & HTML, defect, P1)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1186843
| blocking-b2g | 2.5+ |
People
(Reporter: kanru, Assigned: kanru)
References
Details
To implement the new security model[1] we want to enable the browser-element to use different process for different origins. It seems having different BrowserElementParent for different process is easier to implement. The idea is nsBrowserElement would get the nsIBrowserElementAPI instance from TabParent. [1]: https://wiki.mozilla.org/FirefoxOS/New_security_model
|
||
Updated•9 years ago
|
Priority: -- → P1
|
|
||
Updated•9 years ago
|
blocking-b2g: --- → 2.5+
|
||
Comment 1•9 years ago
|
||
Paul, Kanru, can we have a assignee to follow this issue? thanks.
Flags: needinfo?(ptheriault)
Flags: needinfo?(kchen)
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → kchen
Flags: needinfo?(kchen)
|
|
||
Updated•9 years ago
|
Flags: needinfo?(ptheriault)
|
|
Assignee | |
Comment 2•9 years ago
|
||
We will use only one BrowserElementParent for now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•