You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I marked a web page as "always open this site in" container "A", for example gmail.com always open in Private container
I saved the web page as bookmark
Then I needed to open the page in a container "B" so I clicked with right mouse button on the saved bookmark and chose "open in a new container" -> container "B", for example to open the gmail in Work container
Unfortunately, the page was opened in container A, not B
Actual behavior
If I set a page to "always open this site in ..." then I am not able to use "open in a new container tab" option to change the default container.
Expected behavior
I would expect that using the "always open this site in ..." option will open a web page in a chosen container by default but using the option "open in a new container tab" would change the default behavior so I could open the page in a different container.
Additional informations
No response
Provide a copy of Troubleshooting Information page (optional)
No response
The text was updated successfully, but these errors were encountered:
Before submitting a bug report
Step to reproduce
Actual behavior
If I set a page to "always open this site in ..." then I am not able to use "open in a new container tab" option to change the default container.
Expected behavior
I would expect that using the "always open this site in ..." option will open a web page in a chosen container by default but using the option "open in a new container tab" would change the default behavior so I could open the page in a different container.
Additional informations
No response
Provide a copy of Troubleshooting Information page (optional)
No response
The text was updated successfully, but these errors were encountered: