Bewertungen für Temporary Containers
Temporary Containers von stoically
264 Bewertungen
- Bewertet mit 5 von 5 Sternenvon КЭП, vor 6 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14329427, vor 6 Jahren
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 12786878, vor 6 Jahren
- Bewertet mit 5 von 5 Sternenvon Flengo, vor 6 Jahren
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 14264986, vor 6 JahrenGreat extension to isolate user activity without doing much work by the user, in automatic mode. However, I noticed a few problems.
Right click menu on a link does not provide "open in new temporary container"
Dragging a selected text into the address bar, (which I imagine does something equivalent to opening a new tab, putting that text into the address bar and clicking 'go'.) actually does the whole thing in the same container I am in. This prevents the isolation.
Could this be caused by some settings? I use the recommended settings (Automatic mode and global setting of open cntrl+click or middle click into new container.)Antwort des Entwicklers
geschrieben am vor 5 JahrenThanks! The context menu (right click) on a link should provide that option - and in my case it works. Sometimes HTML/CSS makes text look like links but in fact they are not actually "a-elements" which are needed for the context menu to work. You might want to check at several places and also make sure you didn't deactivate the context menu in the Advanced -> General -> Context Menu preferences. In case the problem persists I'd need more information; feel free to open a new issue on GitHub in this case: https://github.com/stoically/temporary-containers/issues
Dragging text into the address bar is not catched by "Mouse Clicks"-Isolation. You'd need to configure "Navigating in Tabs"-Isolation for that to work. The reason the Navigating-Isolation isn't recommended is that it breaks redirects to 3rd-party domains (e.g. SSO Logins, Payments) which need to be dealt with. - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14145875, vor 6 JahrenThis addon is exactly what i was looking for. It can be configured to open all sites in their own container and most importantly, removing cookies once the tab is closed and keeping them separate from other containers.
I found one tiny annoyance however: when using the extension as a default for all new tabs opened and opening a new tab with either CTRL+T or by clicking the new tab icon, the url field is not focused afterwards, so I have to hit CTRL+L or click the field before i can type a new url. The normal behavior of firefox is to focus the url field after opening a new tab, making it easy to just start typing a new url.
So I just would like an option (or default behavior) that the url field is focused after a new tab is opened, so I can just type the url right after hitting CTRL+T.Antwort des Entwicklers
geschrieben am vor 5 JahrenIn Automatic Mode new tabs should get focus since they are just opened by the Firefox Webextensions API - and it works for me. Maybe it was a fluke in Firefox, but if the problem persists for you I'd need more information about your environment and settings - the best way would be a new issue on GitHub: https://github.com/stoically/temporary-containers/issues. Thanks. - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13861609, vor 6 JahrenSo far the best container extension out there I've found to complement Mozilla's original extension. I love how ridiculously specific the options get, and the Alt-X shortcut (opening a new tab in the same container as the active one) has saved me so much mouse movement.
- Bewertet mit 5 von 5 Sternenvon Pavel1114, vor 6 JahrenУже было думал придётся самому изучать и писать расширение для себя. Но, к счастью, наткнулся на temporary containers. Это именно то что я искал. Спасибо авторам!
- Bewertet mit 3 von 5 Sternenvon Firefox-Benutzer 13962360, vor 6 Jahrenok but supercookies in SiteSecurityServiceState.txt are not cleared!
Antwort des Entwicklers
geschrieben am vor 5 JahrenContainers don't include the HSTS response cache (https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers#What_is_.28and_isn.27t.29_separated_between_Containers) and as such it's not removed when containers itself are removed. Unfortunately no way for Add-ons to clear that cache in any other way. The bug where this decision was made can be found here: https://bugzilla.mozilla.org/show_bug.cgi?id=1253006 - Bewertet mit 5 von 5 Sternenvon mk.pl, vor 6 Jahrengreat. but confusing to configure.
requires more resources but you can configure it to avoid overuse - Bewertet mit 5 von 5 Sternenvon grahamperrin, vor 6 JahrenLooking good with Waterfox –
https://github.com/mozilla/multi-account-containers/issues/929#issuecomment-394054592 - Bewertet mit 5 von 5 Sternenvon The Beard Below My Chin, vor 6 JahrenMagnificent addon! Not a replacement (as I first suspected) but a supplementary tool for Multi-Account Containers and Cookie Auto Delete. Highly configurable, and if Mozilla gets off their ass and fixes bugs we could see an alternative to Private Tab addon. I highly recommend using this with Switch Containers Plus and maybe even Containerise which makes managing multiple containers a breeze.
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13876816, vor 6 Jahren
- Bewertet mit 5 von 5 Sternenvon v00p, vor 6 JahrenFinally a Container extension with enough parameter to fulfill one's particular needs !
- Bewertet mit 5 von 5 Sternenvon OfficialSWS, vor 6 Jahren
- Bewertet mit 5 von 5 Sternenvon Kiko, vor 6 JahrenVery cool extension! I installed it. Kudos!
- Author of "I don't care about cookies" - - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13971475, vor 6 JahrenThis is a perfect add-on! Works exactly how I wanted the default container application to work - keeping my link-clicking more private by opening links in isolated containers.
Just a thought for the clear history feature - I know that you cannot clear based on container which would be ideal, but can you clear history items that are newer than the container open time? i.e. if I open clear-history-container at 11AM, navigate to example.com and click around for a while, then close the container, can you delete all example.com* history that happened after 11AM? Then you aren't wiping the entire site from history, just any clicks during the duration the tab was opened. - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13998033, vor 6 Jahren
- Bewertet mit 4 von 5 Sternenvon freaktechnik, vor 6 Jahren
- Bewertet mit 4 von 5 Sternenvon indig0F10w, vor 6 JahrenGot a tab in container, I went to download a file, everything was good until I removed this addon and closed Firefox. Now on every browser startup there is the same download poping up and there is no way of stopping it.
EDIT: cleaning Firefox with CCleaner fixes this.Antwort des Entwicklers
geschrieben am vor 6 JahrenGlad you figured out a solution. What happens after removing an Add-on is completely out of control for Add-on Developers. If you encounter such Issues, your best bet might be to report them to the Firefox Bugzilla: https://bugzilla.mozilla.org/ - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13991979, vor 6 JahrenThis is definitely an excellent add-on with an excellent documentation. I definitely recommend it!
However, I'm a bit shocked that its github site has been archieved (read-only) since a couple of days. What happened? Does that mean that the project and, hence, this add-on is now abondoned? A short explanation by stoically would be highly welcome!Antwort des Entwicklers
geschrieben am vor 6 JahrenThanks for the kind words!
I've currently not much time to work on the Add-on, but I guess archiving it was the wrong signal. It's unarchived again, but future updates will take some time. - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13230603, vor 6 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13979250, vor 6 JahrenI really like this add-on. It does something I've been searching for for ages. One suggestion I might make concerns the "Navigating in Tabs should open new Temporary Containers" option. It appears that setting that to something other than "Never" results in many websites that use redirects breaking, and requiring you to figure out the names of all the redirects and then putting the original website and the redirects all in the same permanent container with "Never", not set. This is a real pain, and a non-technical user probably wouldn't be able to figure out how to do it, so most people will likely set the global to "Never" in order to avoid the hassle, especially since you can't sync the settings across computers.
However, another side effect of having that set to "Never" appears to be that if you type a new URL into the tab yourself, the new site opens in the same temporary container. That seems to me to be more of an issue than allowing all the redirected sites to use the same temporary container by default, as the behavior the user is probably expecting is that each link they click on or each URL they type into the browser opens in a temporary container, but that stuff that's on the web page where they didn't manually click a link or type something else (e.g. redirects), would share the container. My suggestion here would be to either create a new option to allow the user to decide what to do if a new URL is manually typed into the command area of an existing temporary container, similar to the option given regarding the clicking of links, or simply assume that if the user types a new URL into the command area, that should be construed to be the same as left clicking a link and the same setting would govern both.
I think doing it that way would be a good compromise between maximum privacy and ease of use, as only the very technical and very paranoid would take the trouble to track down all the redirects and create permanent containers for every site with redirects that the non-Never setting breaks, and go through that exercise on every computer they use because the settings don't sync.Antwort des Entwicklers
geschrieben am vor 6 JahrenGlad you like the Add-on. A better way to "unbreak Isolation" than just setting the whole "Source-Page" to "Never" is definitely needed and already on the list, you can follow progress here: https://github.com/stoically/temporary-containers/issues/104
It'll work by also giving a way to "exclude target Domains" from Isolation. In this case, if you type a new URL into the address bar it'll still get "isolated", unless it's one of the explicitly excluded Domains. Differentiating between an explicitly typed into the address bar navigation and a navigation triggered by click or from the tab itself is, afaik, unfortunately not that easy possible. Feel free to comment on the GitHub Issue if you feel the planned changes aren't enough or you have other ideas about how to solve this. - Bewertet mit 5 von 5 Sternenvon matdodgson, vor 6 JahrenThis is exactly the extension I have been wanting to write for several years now but was too lazy. With this extension, we have an isolated browser session per tab (or group of tabs) with very little effort, and the tracking from those sessions die when you close the tab. This nullifies Google and Facebook's business model and sadly we'll never see this as a built in feature in any popular browser. Thanks so much to the developer of the extension!