Open roothorick opened 4 years ago
Unfortunately there's AFAIK no way to differentiate between links opened from an external program and just new tabs. So I don't think this is possible to do yet. Would probably need some sort of API enhancement upstream (in the WebExtensions API, request on Bugzilla).
Is there a way that TC would check if tab is opened/"starting to open" in a default container and would (instantly) reopen into a temporary container in that case?
I am using HTTPZ web extension which tries to reopen a non-TLS (that is http) with TLS (https).
See what happens:
If external URL is already https then HTTPZ does not interfere and the tab lands to default container.
Bear in mind that undesired opening in a default container happen here only when FF is initially closed and freshly opened by invoking external URL. If firefox is already opened from before, then external URL always lands in a temp or permanent container as desired.
Maybe you can check if the Firefox is just started and tab in starting to open in a default container it should reopen.
Just brainstorming 😜
@crssi Normally this already works, but it's a regression in Firefox, see https://bugzilla.mozilla.org/show_bug.cgi?id=1653237
I see, thank you.
Is there something you can do as workaround?
Otherwise I get a feeling of we have humbly to wait and hope it won't get the WONTFIX
status after 2030. 😉
I don't think there's a workaround, bu given that it affects a lot of Add-ons, including Adblockers, and is P2, I'm hopeful that it gets fixed soon.
I want external links opened in temporary containers (which isn't working for me, but I'll make another issue about that), but I use "no container" as effectively another permanent container, which makes full automatic mode counterproductive. I think these functionalities should be separated.