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

Feature request: Container whitelist without assigning sites #1892

Closed
gpoole opened this issue Oct 16, 2020 · 7 comments
Closed

Feature request: Container whitelist without assigning sites #1892

gpoole opened this issue Oct 16, 2020 · 7 comments

Comments

@gpoole
Copy link

gpoole commented Oct 16, 2020

I'd like to restrict containers to open a whitelist of domains, like #1670 and #847, but I also use some sites in multiple containers, so I don't want to actually assign those sites to a specific container. For example, I have a Google account for work and a personal Google account, so I'd like to use the various Google apps with different logins in my "Work" and "Personal" containers. I'd still like to limit my "Work" and "Personal" containers to a whitelist so that links to external sites open in the default container automatically, instead of in the current container.

Thanks to the contributors for their work on this extension, it's a killer feature for Firefox and has motivated me to switch back from Chrome!

@D33M0N
Copy link

D33M0N commented Oct 21, 2020

+1

1 similar comment
@serhumanos
Copy link

+1

@WhyNotHugo
Copy link

I'd love to see this too. I have a dedicated WhatsApp container, and would like any links I click on it to just fall out of that container.

@ncallaway
Copy link

This is something that also has caused me a lot of frustration. I'm working on a pull request for this now and have a proof of concept working.

I expect to have a pull request out for review by next weekend.

ncallaway added a commit to ncallaway/multi-account-containers that referenced this issue Apr 25, 2021
This implements a per-container allow-list that is applied to isolated
containers. This can allow multiple containers to have an overlapping set of
sites that they are isolated to.

For example: Container A and Container B could both be isolated and have
calendar.example.com in their allow list. Both Container A and Container B
would then be able to visit calendar.example.com.

See: mozilla#1892 and
mozilla#1887 for additional
motivation.
ncallaway added a commit to ncallaway/multi-account-containers that referenced this issue Apr 25, 2021
This implements a per-container allow-list that is applied to isolated
containers. This can allow multiple containers to have an overlapping set of
sites that they are isolated to.

For example: Container A and Container B could both be isolated and have
calendar.example.com in their allow list. Both Container A and Container B
would then be able to visit calendar.example.com.

See: mozilla#1892 and
mozilla#1887 for additional
motivation.
@ncallaway
Copy link

Draft PR is out here: #2033. Remaining work is just the new icon and any PR feedback, which I'll work on this week.

@ncallaway
Copy link

The related PR is now ready for review.

@dannycolin
Copy link
Collaborator

Duplicate of #1749

@dannycolin dannycolin marked this as a duplicate of #1749 Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants