Security/B2G/Browser API: Difference between revisions

no edit summary
(Created page with "{{SecTracker |Component=Browser API }} {{SecTrackerItem |Sectrackerstatus=OK |Simpyn=No |SecTrackerFSA=no }} https://bugzilla.mozilla.org/show_bug.cgi?id=693515 https://etherp...")
 
No edit summary
Line 7: Line 7:
|SecTrackerFSA=no
|SecTrackerFSA=no
}}
}}
https://bugzilla.mozilla.org/show_bug.cgi?id=693515
[Category:WebApi]]
 
===Background===
https://etherpad.mozilla.org/BrowserAPISec
Goals
 
* Provide support so that a Browser can be implemented as a Web App
[[Category:B2G]]
* Implemented as new type of iframe which provides limited cross-origin access so that a page embedding this iframe can act like a web browser.
* Being implemented with a minimal set of APIs to
Specification:
* https://wiki.mozilla.org/WebAPI/BrowserAPI
Bugs:
* https://bugzilla.mozilla.org/show_bug.cgi?id=693515
Pages:
Source:
===Data Flow Diagram===
===Answered Questions===
===Open Questions===
Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?
===Threat Model===
===Authorization Model===
*Implicit: An app will need to granted the browser permission
===Implementation Requirements===
*Many, TBD.
canmove, Confirmed users
1,220

edits