On 22/01/15 13:20, Ehsan Akhgari wrote: > On 2015-01-21 2:27 PM, Steve Workman wrote: >> https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers >> <https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers> >> >> We're currently doing some user research to figure out how we might do >> this best. > > Obviously there is a ton of UX level stuff that we need to figure out, > and I think that wiki page does a good job discussing them. But it's > also discussing appId here, which confuses me. What do containers and > appId have to do with each other? Based on reading the UX proposal > there, my intuition is that this feature will be implemented on top of > separate profiles, perhaps that's not what was intended?
Containers would be implemented on top of appId (or a similar mechanism) so that it's lightweight and that things like bookmarks and history are shared. User profiles would be a revamped version of browser profiles: https://wiki.mozilla.org/Security/Contextual_Identity_Project/User_Profiles >> A separare profile would be best yes, but being able to quickly open up >> an isolated, disposable, fresh session could be useful for developers. > > I completely agree, but that doesn't preclude the usage of a new > profile, right? The perceived disadvantages of using a different profile in this case were: - you need to create a profile on disk, just to trash it later - you can't share history and bookmarks - a new Firefox process is started per profile Francois _______________________________________________ dev-privacy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-privacy
