On Mon, Mar 7, 2016 at 1:55 PM, J. Ryan Stinnett <jry...@gmail.com> wrote: > By default, <iframe mozbrowser> can't access the storage used by > <xul:browser> for cookies and other site data, making it hard to share page > state across the two browser frame types. An additional feature <iframe > mozbrowser noisolation> has been added, which gives the frame access to the > same storage as <xul:browser>. This is only meant for use on desktop > Firefox to allow HTML and XUL browser frames to work together.
Is there a reason we couldn't make 'noisolation' the default behavior when <iframe mozbrowser> is used by chrome code? There is currently work going on in Gecko to enable use of multiple "cookie jars" in Firefox, this is heavily based on the cookie jar implementation that we wrote for FirefoxOS, but it is cleaned up and simplified. I suggest we use that support rather than the old FirefoxOS cookie jars. The main reason is that you'll have to deal with painful data migration once the new isolation is fully in place. In practice I expect all data in other cookie jars to be deleted rather than migrated at some point in the future. So what I'm suggesting is: * Make <iframe mozbrowser> act as if 'noisolation' is set when the element is used in chrome documents (documents with a system principal). * Add support for <iframe mozbrowser usercontextid=X> similar to <xul:browser usercontextid=X> which already exist. Sorry for not noticing this earlier in the new <iframe mozbrowser> work. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform