Closed Bug 1186296 Opened 5 years ago Closed 5 years ago

Manage nsIBrowserElementAPI in TabParent

Categories

(Core :: DOM: Core & HTML, defect, P1)

defect

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
blocking-b2g: --- → 2.5+
Paul, Kanru, can we have a assignee to follow this issue? thanks.
Flags: needinfo?(ptheriault)
Flags: needinfo?(kchen)
Assignee: nobody → kchen
Flags: needinfo?(kchen)
Flags: needinfo?(ptheriault)
We will use only one BrowserElementParent for now.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1186843
You need to log in before you can comment on or make changes to this bug.