You're right about the limits of containers. When I'm browsing normally, the default is not to be logged into Google, Twitter, Facebook, etc. Things like my "Gmail this" bookmark fail because I set up Gmail in its own container.
However, I find it very useful to have specific containers for Facebook, banking, other social networks, most of my gmail accounts, etc. So I can be doing stuff for my son's soccer club's email without it affecting my own gmail.
I think of containers as a user tool. It seems like profiles are more of a developer tool.
> So I can be doing stuff for my son's soccer club's email without it affecting my own gmail.
In Chrome you could click on the profile icon in the top right and add a profile "Son's soccer club", and I believe that would also prevent it affecting your Gmail, etc.
> I think of containers as a user tool. It seems like profiles are more of a developer tool.
In Firefox, yes it seems like it. But not in Chrome. The point I'm trying to make (if by any chance there are Firefox people listening!) is that Firefox would benefit from making their hidden profile feature easily available to users, as Chrome does. But then they'd have the confusion of containers vs profiles, so it seems that they should just make containers behave like Chrome's profiles. But Firefox has Profiles! So why did they introduce Containers? IOW it honestly seems like they've made a mess there and the Firefox would be improved by fixing that mess.
However, I find it very useful to have specific containers for Facebook, banking, other social networks, most of my gmail accounts, etc. So I can be doing stuff for my son's soccer club's email without it affecting my own gmail.
I think of containers as a user tool. It seems like profiles are more of a developer tool.