search

kintesh / containerise

Firefox extension to automatically open websites in a container
MIT License
408 stars 54 forks source link

Limit containers to **only** certain domains #142

Open diego898 opened 3 years ago

diego898 commented 3 years ago

I can add rules to make domains always open in their container, but how can I make it so that only those urls open in that container?

For example, I only want google urls in the google container

tsbertalan commented 9 months ago

This seems pretty crucial--MAC is basically unusable for any google things, due to google's many Byzantine redirection structures, so you need things like .google.com, .withgoogle.com, .gstatic.com, etc; hence containerise. However, in order to prevent e.g. a Google search or a link from gmail to contaminate all downstream tabs, I need to allow only* matching tabs to reuse the container.

tsbertalan commented 9 months ago

Enabling the Default Container and "Keep Old Tabs" options seems to be a good workaround for me, but if there's a better option available, I'd still like to know.

kupietools commented 6 months ago

This plugin is unfortunately useless to me because of this issue. I wanted to segregate Google in its own container, but all I end up with is dozens of tabs from different domains, all opened from Google's search results, all in Google's container, exactly where I don't want domains besides Google.

"Default container" isn't a good workaround, as it creates yet another container and now new tabs can't see all my saved cookie logins. "No container" has to be the default, and links opened from Google search have to be opened in "No container".

tsbertalan commented 3 months ago

An update--after adding lots of patterns to my google (and microsoft) containerize groups with the network.http.redirection-limit trick, and enabling Default Containers, I mostly seem to have this under control now. (With the minor annoyance that new windows always open a second tab after I type a url and press enter.) @kupietools , I don't quite understand the objection about cookies--surely you don't want to be sharing your container cookies with the no/default container tab, right?