Security/B2G/Browser API: Difference between revisions

Revision as of 03:34, 3 May 2012

Please use "Edit with form" above to edit this page.

{{#set:Component=Browser API |Project=` |Milestone=` |Resource=` }}

Status:	OK
Securtiy Approved for Beta Launch?:	No
Data Flow Diagram:	`
Threat Model:	`
Bugs:	`
Security Review:	`
Final Security Approval:	no

{{#set:Sectrackerstatus=OK |Simpyn=No |DFD=` |TM=` |bugs=` |Secreview=` |SecTrackerFSA=no }} [Category:WebApi]]

Goals

Provide support so that a Browser can be implemented as a Web App
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:

Bugs:

Pages: Source:

Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?

@@ Line 7: / Line 7: @@
 |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.