3 ms·
I've used these for over a year. Where the experience falls short is when using OAuth flows where either the requestor or provider is in a different container.
by pbowyer 4y ago
I've used these for over a year. Where the experience falls short is when using OAuth flows where either the requestor or provider is in a different container.
E.g. Slack (work) => Twitter (social media) => ~~broken~~ as the redirect doesn't go back to the (work) container.
I can't think of a fix because any there is would break the privacy of containers.
- thomastjeffery 4y agoYou can right click a link, and open it in the other container. It's clunky, but has worked for me so far. The UX for default containers could really benefit from some kind of context-awareness, but I'm not sure what that would look like. I'm thinking an intermediary tab that gives you a list of default containers (instead of only a single option or none at all) to choose from when opening a domain. Then, maybe, you could set a default choice based on the originating container. Or maybe a tree of sub-containers... This is where addon-defined UX makes sense.
- jedberg 4y agoThe workaround I've used is to open slack.com in the Google container, etc. Not ideal, but it works. In some cases though I do have to switch my default browser to Chrome, log in, then switch it back.