Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] default containers, grouping containers #1477

Closed
alsoeric opened this issue Aug 12, 2019 · 3 comments
Closed

[Feature request] default containers, grouping containers #1477

alsoeric opened this issue Aug 12, 2019 · 3 comments

Comments

@alsoeric
Copy link

Two features that might be useful. The first is designating a named container as the default container.
The second feature is organizing containers to a window. Any time you open a container, that tab is moved to the window containing tabs of the same container.

@minmazeb
Copy link

I endorse both of these suggestions.

While it is easy enough to open a tab in the appropriate container prior to visiting a page under normal browsing circumstances, the need for a user-definable default container is apparent when I click on a link in a non-browser application, which then triggers the OS to send the url to my default browser (firefox) for processing. Firefox opens such links in a non-contained context, which is not what I desire.

The second suggestion above could be tricky to design, my first approach were I to attempt an implementation (sadly, unlikely to occur) would be a little different than @alsoeric wrote. Instead of moving container tabs automatically to existing windows that already possess tabs associated with that container, I would simply add an option to prohibit any single window from hosting tabs from multiple different containers. If a tab were otherwise to be created in a window, but the new tab's container isn't the same as all of the existing tabs in that window, a new window would be created to host the new tab. In other words, if it's too difficult or time consuming to select the appropriate window to add the tab to (I can think of a few edge cases that would be problematic) it's sufficient in my opinion to at least NOT add it to an inappropriate one.

@bondsbw
Copy link

bondsbw commented Sep 12, 2019

@minmazeb

I would simply add an option to prohibit any single window from hosting tabs from multiple different containers

I agree with this approach.

I also use the extension Container Color Theme which changes the full browser color based on your container. Then it's easy to use window previews (e.g. the Windows taskbar or Alt-Tab) to figure out which window is which container set.

But that doesn't work so well if I click on an email link and it opens in the default container within some window that I've been using for a named container.

@kendallcorner
Copy link
Collaborator

Thanks for the input. These suggestions look like #356 and #319. Please vote (:+1:) or discuss on those issues so they are more likely to be completed. I'll close this, but feel free to reopen if you think these are different issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants