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

Bug: When a site is configured to always open, opening a bookmark with a specific container doesnt work. #2345

Closed
Hobbit44 opened this issue Apr 28, 2022 · 3 comments
Labels
Status: Expected This behavior is expected of the add-on

Comments

@Hobbit44
Copy link

  • Multi-Account Containers Version: 8.0.7
  • Operating System + Version: Windows 11 Pro 22593.1
  • Firefox Version: Nightly
  • Other installed Add-ons + Version + Enabled/Disabled-Status: N/A

Steps to reproduce

  • Save site as bookmark
  • Set site to Always open in container A
  • Right click the bookmark and say "open in container B"

Actual behavour:
It still opens in the container A

Expected behaviour:
Link opens in container B

@chrisbudden
Copy link

I have a silmiar issue - this is my use case -

I have 'portal.azure.com' set to open in a sepcific container as this is primarialy where I need to use Azure, but sometimes i need to use Azure in another container with a different account. If i specifically open a new tab with the secondary container and load the URL, it changes to the primary container rather than the secondary.

Thanks.

@dannycolin dannycolin added the Status: Expected This behavior is expected of the add-on label Aug 6, 2022
@dannycolin
Copy link
Collaborator

That'd be the expected behavior of the addon. There's already #1133 that is asking the context menu has priority over the "Always open in Container X" option. So I'll close this issue as a duplicate of it.

@dannycolin
Copy link
Collaborator

Duplicate of #1133

@dannycolin dannycolin marked this as a duplicate of #1133 Aug 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Expected This behavior is expected of the add-on
Projects
None yet
Development

No branches or pull requests

3 participants