3 ms·
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 amo
by TheMiller 7y ago
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.
- rsync 7y ago"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.
- guelo 7y agoThat makes a lot of sense, same as private browsing which opens a new window.