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
set containerise to open "www.youtube.com" and "*.youtube.com" in that container;
try logging in on Google outside of that container.
Actual behaviour:
I set up Containerise to always open YouTube pages in a specific container - let's call it the "YT container" That won't work by setting "www.youtube.com" and requires "*.youtube.com" to be used instead. Alas this has further implications as the login process on Google seems to call YouTube as well; Containerise shifts the tab to the YT container and the user finds themselves logged in on both the original container and the YT container, which is exactly what one would want to avoid when setting up a container in the first place.
Expected behaviour:
Containerise manages "www.youtube.com" without having to resort to use wildcards. On top of this, when one logs in on Google, this does not logs them in in the YT container.
The text was updated successfully, but these errors were encountered:
Containerise Version: 3.7.0
Operating System: KDE neon (Ubuntu-based), 64-bit
Firefox Version: 79.0
Steps to reproduce:
Actual behaviour:
I set up Containerise to always open YouTube pages in a specific container - let's call it the "YT container" That won't work by setting "www.youtube.com" and requires "*.youtube.com" to be used instead. Alas this has further implications as the login process on Google seems to call YouTube as well; Containerise shifts the tab to the YT container and the user finds themselves logged in on both the original container and the YT container, which is exactly what one would want to avoid when setting up a container in the first place.
Expected behaviour:
Containerise manages "www.youtube.com" without having to resort to use wildcards. On top of this, when one logs in on Google, this does not logs them in in the YT container.
The text was updated successfully, but these errors were encountered: