I don't get why this lives in an extension. It's even advertised in the options, but requires downloading a separate component. Creating an awkward experience as what looks like a core feature lives in an external module. I imagine there is a non-zero number of users who look at containers then opt not to use it because of the download requirement.
I do get it. I've been using it for several months, and I run into problems fairly often. Nothing wrong with the implementation, AFAICT, but it takes a fair amount of thought to assign sites to different containers, and you can easily end up following links that cross container boundaries and then don't work right because of the context change. I've even run into several corporate sites where federated authentication simply won't work in a container, at all.
"I do get it. I've been using it for several months, and I run into problems fairly often. Nothing wrong with the implementation, AFAICT, but it takes a fair amount of thought to assign sites to different containers, and you can easily end up following links that cross container boundaries and then don't work right because of the context change."
See my comment above - I think the obvious workflow for containers is a container window, not a tab, and all tabs created in that window inherit the container settings.
As I also note, above, I don't see how to manage per-container cookies and history ... I can't clear history for just my "banking" container (or whatever).
I really want to make heavy use of a container-like feature but keep stumbling over things like this.
