ctrl + shift + # as is current behaviour.The user then has the several ways to open a new tab in another container including:

Therefore, I think hitting ctl + t should also assume the current container to be the default context and open a new tab in that container.

My logic is clicking a link that should open in a new target window/tab opens a tab in the same container, so the current container is assumed to be the default in this context. You're in a tab in container X, you open new tab, it's in container Y (or none), either way not the 'current' container. I'm not using tabs across windows personally. ctrl + t is the simplest way other than clicking the button.Īgreed I'm not sure about the window default though. Making users change to using a different shortcut seems like a bad cx for the feature. This could be something like #849, (where I'm prompted for a choice if I go to a url that's assigned to multiple containers) or it could just be a keyboard shortcut that reloads my current tab with a different container.Īnyways, I'm going to unfollow this issue but thought I would voice my thoughts before I leave.Įdit: I just saw which eliminates the reloads idea but I believe a prompt before loading the URL could still be viable. Now what I desire is a seemless way to switch my current tab to another container. To go one step further, I think that the option to open new tabs in the same container would muddle this feature and would make it more difficult for new users to understand containerization (and that its strictly not related to about:profiles or about:accounts). I now disagree with my original assumption and now think that new tabs and windows should always open in the default container. Now, after using it for a few weeks, I feel like I have a better understanding of this feature, and the enhancements that would make it perfect for my browsing behaviors. After discovering and installing this add-on, I up'ed and followed this issue.

Firefox opening multiple tabs