[Bug] Trying to manually open a tab in a different container when the container is fixed.

[naoliden]

Trying to manually open a tab in a different container when the container for that site is fixed doesn't work.
For example:
I have youtube set to always open in a specific container, but if I ever want to open youtube in a different container (with different credentials), it won't work. Even if I do it manually with the option "reopen in this site in ...". It reopens it in the same preset container.
To go around this I have to sign in in private mode, which is not really a solution.

[ronzie]

The same thing happened to me on walmart.com. I can find no way to rescind the "always open in this container" setting. I am using version 7.3.0 of the addon with Firefox 87.0 (64bit) on Windows 10 Home,
Version 20H2, build 19042.870, Windows Feature Experience Pack 120.2212.551.0

[fuglede]

Another (probably insufficient) workaround is to simply disable the site rule, cf. #1999 (comment)

[ronzie]

"Insufficient" is not the word I'd use, but it's a polite version of what I would say! :) Thanks for pointing it out!

[chli]

Is this a new bug ? As far as I can tell that was always the implemented behavior ? However it never matched my desired use case.

Typically I'm browsing the web in throw-away containers but sometime I want to use my "Google Connected" container or other online shopping containers where I previously connected with the website's user account. So I would like to "always open google.com in my "Google Not Connected" container and sometime re-open Google.com in a "Google Connected Container". I don't think that behavior was ever implemented (e,g, forcing a specific container on request). I don't want to have to confirm my choice ever.

Thanks !

[TonyGravagno]

@chli I believe your use case is handled with the settings from the toolbar. I believe you can also open the current tab (google.com) in a specific container using some combination with the numeric keypad. See Firefox options > Tabs.

The workaround referenced by @fuglede allows us to remove a URL associated with a container, which is a good solution to a different problem.

The problem reported in this thread is about opening in a different container while leaving the association. The prompt "Open this site in your assigned container" provides us with a temporary or permanent override. The responses to the fields on that page do not seem to be respected. OR There was another issue reported aroun 2017-2019 where JavaScript service workers were being used in sites and people could not open those site in containers. It seems to me that something in that area seems to be happening again, since @ronzie reported it's happening with a specific site.

I hope some of this connecting of dots helps the developers.

[chli]

Maybe I wasn't clear but I think my use case is the same as the one reported as a "bug" here, however I don't think it's a new bug cause it's always the behavior I had.

So when I type google.com in my address bar I have the Multi-Account Container extension setup so that it opens in my "Google Not Connected" container (by default) but sometime I want to access my google account preferences so I want to open Google.com in my "Google Connected" container. AFAIK this is not possible using the menu "Reopen this site in..." cause it reopens it in the default "Google Not Connected" container. What I want is that the "Reopen this site in..." forces to open Google.com in the specified container for that one time.

[grahamperrin]

Duplicate of 2019 issue #1442

[grahamperrin]

▶ #1222 and/or #1414

@naoliden please consider closing this duplicate, so that others can be more easily managed. Thank you.

[grahamperrin]

Thanks!