Pógódnośenja za Temporary Containers
Temporary Containers wót stoically
236 pógódnośenjow
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 14441753, 6 tahun yang lepas
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 14432039, 6 tahun yang lepasOptions were a little confusing to setup, but overall this is a fantastic extension and it's a shame that this functionality wasn't in the official multi-container extension to begin with.
- Z 5 z 5 pógódnośonywót Fruchtenstein, 6 tahun yang lepas
- Z 5 z 5 pógódnośonywót claustromaniac, 6 tahun yang lepas
- Z 5 z 5 pógódnośonywót asras, 6 tahun yang lepasFreaking amazing [idea, implementation, and] use of Firefox's containers. Thank you!
- Z 5 z 5 pógódnośonywót pedz, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót КЭП, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 14329427, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót Flengo, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 14145875, 7 tahun yang lepasThis 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.Wótegrono wuwijarja
jo se napisał 6 tahun yang lepasIn 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. - Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13861609, 7 tahun yang lepasSo 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.
- Z 5 z 5 pógódnośonywót Pavel1114, 7 tahun yang lepasУже было думал придётся самому изучать и писать расширение для себя. Но, к счастью, наткнулся на temporary containers. Это именно то что я искал. Спасибо авторам!
- Z 5 z 5 pógódnośonywót mk.pl, 7 tahun yang lepasgreat. but confusing to configure.
requires more resources but you can configure it to avoid overuse - Z 5 z 5 pógódnośonywót grahamperrin, 7 tahun yang lepasLooking good with Waterfox –
https://github.com/mozilla/multi-account-containers/issues/929#issuecomment-394054592 - Z 5 z 5 pógódnośonywót The Beard Below My Chin, 7 tahun yang lepasMagnificent 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.
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13876816, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót v00p, 7 tahun yang lepasFinally a Container extension with enough parameter to fulfill one's particular needs !
- Z 5 z 5 pógódnośonywót OfficialSWS, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót Kiko, 7 tahun yang lepasVery cool extension! I installed it. Kudos!
- Author of "I don't care about cookies" - - Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13971475, 7 tahun yang lepasThis 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. - Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13998033, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13991979, 7 tahun yang lepasThis 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!Wótegrono wuwijarja
jo se napisał 7 tahun yang lepasThanks 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. - Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13230603, 7 tahun yang lepas
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13979250, 7 tahun yang lepasI 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.Wótegrono wuwijarja
jo se napisał 7 tahun yang lepasGlad 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.