Changes

Jump to: navigation, search

Apps/Security

4 bytes added, 05:48, 9 August 2012
no edit summary
But just like for websites today, a webpage which contains an <iframe> pointing to a different origin can't reach into that iframe and modify or touch the objects there. And like with normal websites, permissions are separated by origin, meaning that just because a permission is granted to an app, doesn't mean that any <iframe>s that that app opens has access to the same permissions.
 
=== Data management ===
 
appid/browserContent flag in B2G
separate profiles on desktop/android
 
=== Process sandboxes ===
==Application Lifecycle==
There is no way for privileged apps to relax this policy. However we may in the future add the ability for packaged apps to define their own CSP policies, in which case that would allow apps to apply more restrictive policies. However such policies would be merged with the above policy which means that it still wouldn't allow the app to relax the policy.
 
== Data management ==
 
appid/browserContent flag in B2G
separate profiles on desktop/android
 
== Process sandboxes ==
==Out of scope for 1.0==
Confirm
717
edits

Navigation menu