Отзывы на Temporary Containers
Temporary Containers от stoically
265 отзывов
- Оценено на 5 из 5от pedz, 6 лет назад
- Оценено на 5 из 5от КЭП, 6 лет назад
- Оценено на 5 из 5от Пользователь Firefox 14329427, 6 лет назад
- Оценено на 4 из 5от Пользователь Firefox 12786878, 6 лет назад
- Оценено на 5 из 5от Flengo, 6 лет назад
- Оценено на 4 из 5от Пользователь Firefox 14264986, 6 лет назадGreat 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.)Ответ разработчика
размещено 5 лет назадThanks! 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. - Оценено на 5 из 5от Пользователь Firefox 14145875, 6 лет назадThis 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.Ответ разработчика
размещено 5 лет назадIn 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. - Оценено на 5 из 5от Пользователь Firefox 13861609, 6 лет назадSo 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.
- Оценено на 5 из 5от Pavel1114, 6 лет назадУже было думал придётся самому изучать и писать расширение для себя. Но, к счастью, наткнулся на temporary containers. Это именно то что я искал. Спасибо авторам!
- Оценено на 3 из 5от Пользователь Firefox 13962360, 6 лет назадok but supercookies in SiteSecurityServiceState.txt are not cleared!
Ответ разработчика
размещено 5 лет назадContainers 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 - Оценено на 5 из 5от mk.pl, 6 лет назадgreat. but confusing to configure.
requires more resources but you can configure it to avoid overuse - Оценено на 5 из 5от grahamperrin, 6 лет назадLooking good with Waterfox –
https://github.com/mozilla/multi-account-containers/issues/929#issuecomment-394054592 - Оценено на 5 из 5от The Beard Below My Chin, 6 лет назадMagnificent 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.
- Оценено на 5 из 5от Пользователь Firefox 13876816, 6 лет назад
- Оценено на 5 из 5от v00p, 6 лет назадFinally a Container extension with enough parameter to fulfill one's particular needs !
- Оценено на 5 из 5от OfficialSWS, 6 лет назад
- Оценено на 5 из 5от Kiko, 6 лет назадVery cool extension! I installed it. Kudos!
- Author of "I don't care about cookies" - - Оценено на 5 из 5от Пользователь Firefox 13971475, 6 лет назадThis 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. - Оценено на 5 из 5от Пользователь Firefox 13998033, 6 лет назад
- Оценено на 4 из 5от freaktechnik, 6 лет назад
- Оценено на 4 из 5от indig0F10w, 6 лет назадGot 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.Ответ разработчика
размещено 6 лет назадGlad 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/ - Оценено на 5 из 5от Пользователь Firefox 13991979, 6 лет назадThis 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!Ответ разработчика
размещено 6 лет назадThanks 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. - Оценено на 5 из 5от Пользователь Firefox 13230603, 6 лет назад
- Оценено на 5 из 5от Пользователь Firefox 13979250, 6 лет назадI 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.Ответ разработчика
размещено 6 лет назадGlad 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.