Chromium code has the concept of a "Profile". All renderers are associated
with a profile. There is one cookie store per profile.
By default, renderers are all given the same profile. When you use
Incognito mode, for the purposes of cookies you can think of it like
creating a new profile which will never be saved to disk, so Incognito tabs'
cookie stores are distinct from non-Incognito tabs.
>From a UI point of view we don't allow tabs from separate profiles to
cohabit the same window. Thus to the user it appears we have Incognito vs.
non-Incognito windows, not tabs.
There is code in place to provide some basic UI for having multiple
(non-Incognito) profiles. It's off by default. There are probably bugs and
the user experience isn't good. The closest bug about providing a good UX
for this functionality is crbug.com/812 . There is no timeframe on that
work, or necessarily even agreement that it will ever happen.
PK
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
