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
Click the extension icon.
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
The text was updated successfully, but these errors were encountered:
Before submitting a bug report
Step to reproduce
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
The text was updated successfully, but these errors were encountered: