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

No way to configure "always open this site in" default container #2520

Closed
2 tasks done
gentoo-root opened this issue Mar 28, 2023 · 2 comments
Closed
2 tasks done

No way to configure "always open this site in" default container #2520

gentoo-root opened this issue Mar 28, 2023 · 2 comments
Labels
bug Something is broken!

Comments

@gentoo-root
Copy link

Before submitting a bug report

  • I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
  • I searched for existing reports to see if it hasn't already been reported

Step to reproduce

  1. Click the extension icon.
  2. Click "Always Open This Site in...".

Actual behavior

The list of containers is shown, but the default container (no container) is not in the list.

Expected behavior

I would expect "no container" to show up in the list to be able to force some sites to open in the default, non-containerized way, when I navigate there by a link from a containerized tab.

Use case: I use most of the sites outside of containers, log into accounts, etc., and when some link in a containerized tab leads me to some site where I have an account, I would like it to open in the "default" container (i.e. no container). However, right now it's only possible to make it open in another container.

Additional informations

No response

Provide a copy of Troubleshooting Information page (optional)

No response

@gentoo-root gentoo-root added the bug Something is broken! label Mar 28, 2023
@ColonelGerdauf
Copy link

I previously achieved this via IIRC a hack via about:config, but I have forgotten, and the Firefox setup got lost to time and data corruption.

@dannycolin
Copy link
Collaborator

Duplicate of #503

@dannycolin dannycolin marked this as a duplicate of #503 Apr 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken!
Projects
None yet
Development

No branches or pull requests

3 participants