On Mon, Mar 7, 2016 at 10:35 PM, Tim Guan-tin Chien <timdr...@mozilla.com> wrote: > I am confused. In your proposal, are you referring to the chrome > *user/embedder* of <iframe mozbrowser> (e.g. shell.html), or a chrome > *embedded* page (I am not aware of any example).
What I'm saying is that in pages that run with chrome privileges (like shell.html or browser.xul) <iframe mozbrowser> will *not* change which cookie jar is used. I.e. the appid/browserflag would be the same as for the chrome page. When <iframe mozbrowser/mozapp> is used in non-chrome pages, which currently is only possible to do using FirefoxOS privileged and certified apps, then it would behave as it does today and thus change which cookie jar is used. Sounds like FirefoxOS is migrating to using chrome for the system app and maybe a few other apps. I.e. this content will stop being run as privileged/certified apps and will instead be run as chrome. If that's the case then either way it will affect which cookie jar is used by these apps. And it would also mean that it affects which cookie jar is used by content inside the <iframe mozbrowser> used by this content. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

