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

Automatic mode incompatibility with new "restrict" feature of Containers #439

Closed
YoAm opened this issue Jul 12, 2020 · 3 comments
Closed

Comments

@YoAm
Copy link

YoAm commented Jul 12, 2020

When restricting a container to specific sites, and opening a link from within that container, the new tab is placed in no container.

@stoically
Copy link
Owner

Have to look into how MAC implemented it, but I think that can't and probably shouldn't be covered by automatic mode. A workaround that should work is using isolation.

@stoically
Copy link
Owner

Though, the automatic mode description reads "Tab tries to load a website in no container", so maybe it should be covered after all :D

Related: #432 (comment)

@crssi
Copy link

crssi commented Jul 12, 2020

I am using per domain isolation rule as last of rules to catch cases which would land to non-isolated containers:
Domain: *
Always open in: Enabled

Maybe you can try that?
Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants