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 requests #741

Closed
Zlewness opened this issue Aug 18, 2017 · 1 comment
Closed

Feature requests #741

Zlewness opened this issue Aug 18, 2017 · 1 comment

Comments

@Zlewness
Copy link

Hello, I know there are some very similar enhancement requests to this but could it be possible to add the following?

  1. Exclusive containers option: For example if I have a container for "google.com" and middle click links to a few not-google results (to open in a new tab), can it let me kick the new tabs out of the google container automatically? If I click a link in the container, it should convert it back out of the google container, if I press back it should convert it back into the google container (or give a warning).

  2. Wildcards option: Is it possible to set a wildcard/negative container for any site that isn't already defined in containers? (This matches/extends issues Consider making relatedTab not abide to current tab container #434 Add ability to set a default container for new windows and tabs #573 ).

  3. Same as above but if it matches/does not match a certain pattern (eg. "maps.google.*" or "maps.google.tld")? (This matches issue “Always Open in This Container” for entire domains/to include subdomains? #473 Always open URLs that match a pattern in a container #691 )

  4. Temporary containers option: Is it possible to have some sort of temporary container option, sort of like how Private Tab works right now, when the last instance of the container is closed it deletes all history/cookies/cache for it? (Default Firefox also does this with private windows, when the last window is shut the "session" is ended)

@jonathanKingston
Copy link
Contributor

  1. Is covered by "Open always in no container" setting #503
  2. is likely covered by Disable history per-container setting #47 and Allow per-container privacy settings #318

Given there are similar bugs for all these requests is it safe to say this can be closed?

Please let me know if this isn't the case.

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

2 participants