search

stoically / temporary-containers

Firefox Add-on that lets you open automatically managed disposable containers
https://addons.mozilla.org/firefox/addon/temporary-containers/
MIT License
852 stars 60 forks source link

Open in a temporary container always, unless I hold ctrl #385

Open zdat opened 4 years ago

zdat commented 4 years ago

I want to always open in a temporary container, unless I ctrl+click, or ctrl+middle mouse.

I haven't really got this extension figured out yet. Is what I am asking possible?

stoically commented 4 years ago

You could enable Automatic Mode and configure Left Mouse Click Isolation (to e.g. Different from Tab Domain) - that would mostly achieve what you're asking for; however mouse click isolation isn't that reliable, so I guess it would be a nice to allow relaxing/disabling Navigation Isolation for specific mouse clicks.

stoically commented 4 years ago

Ah, wait - is what you're asking for that if you're already in a temporary container and ctrl/middle-mouse click a link, that it opens in the default container (no container)?

zdat commented 4 years ago

Yeah sorry not having any luck with that. It just continues to open in the temporary tab no matter what I change.

however mouse click isolation isn't that reliable

It just seems like you linked back here?

Same when I isolate a domain, then change to Mouse Click options to Never, so I can still open it normally. It opens in a temporary tab no matter what I press.

Basically it just seems like the Mouse Click options don't work for me at all unless I'm not understanding.

Also there's the option "Exclude Permanent Containers". Unfortunately most of my site cookies aren't in a container. They're just stored in Firefox without one. (Currently trying to figure out how to move them all to a container, if you know a way that'd be great).

Is there any way to have this extension see which site cookies you have stored and then make those sites open normally and isolate the rest? Wouldn't mind doing it manually either but I can't figure it out tbh.

crssi commented 4 years ago

Just as a debate which could lead to a solution... why would you sometimes like to open outside a container and not always in a container?

zdat commented 4 years ago

No reason really. Ideally I'd find a quick way to move my accounts with cookies into one then just exclude it.

I don't know a way so I thought if I want to open one of my accounts with cookies, I ctrl + click. Want it without cookies in a container? Just open it normally. Everything else is in the temporary containers too.

crssi commented 4 years ago

For that exact reason I am using Containerise, which nicely complements TC. 😉

Cheers

zdat commented 4 years ago

Actually guys I got it working in a way that I'm fine with for now. Sorry I should have messed around a bit more before posting.

Advanced > Ignoring requests to > then I put my sites with cookies there.

Still can't figure out the Mouse Clicks though.

I'll take some time to try and understand everything.

stoically commented 4 years ago

It just seems like you linked back here?

Sorry, meant to link #184

Same when I isolate a domain, then change to Mouse Click options to Never, so I can still open it normally. It opens in a temporary tab no matter what I press.

"Never" just ignores the mouse click completely and doesn't isolate it. And with "Automatic Mode" enabled, TC will put everything that tries to load in the default container into a temporary container automatically - only way around that, as you correctly figured out - is to put domains into "Ignoring requests to".

Basically TC currently only really covers the use-cases

The use-case to put everything into TCs but some things into the default container isn't really covered.

zdat commented 4 years ago

Thanks. Well I'm reasonably content with my current setup, but is there any way that I can make a site that is set to open in TC, not open in TC using a mouse click, or any way at all?

stoically commented 4 years ago

You mean in case it's set to "Always open in" using "Per Domain Isolation"? No, that's either enabled or disabled.

At some point in time I'd like to refactor the whole "Isolation" thing to allow adding arbitrary rules with "source > cause > action" freely definable (kind of how Request Control does it) - but that'd be a fair chunk of work.