Live data from Hacker News

Guide to Firefox Containers (2018)

thechiefmeat.com

121–130 of 142 posts

Re: Guide to Firefox Containers (2018)

#122
post #120

Earlier quoted context omitted.

Not a container user so I hope you don't mind me asking, how is this different to opening facebook in new private tab/window? Is the convenience in the act of automatically opening it in container if you type in facebook.com or follow a link to it?

what you mention is one advantage, another example is that you are not limited to 2 contexts (private tab & non-private tab vs as many containers as you need). Related to the advantage you mention is also the reverse: clicking a non-facebook link from the facebook container can (if you want) open a non-facebook container

Ok starting to understand it. Seems like something I would have a hard time explaining to a non-tech person.

Re: Guide to Firefox Containers (2018)

#123

The real gem is this extension: Temporary Containers https://addons.mozilla.org/en-US/firefox/addon/temporary-con... Basically every new tab is a new temporary container. Isolation all the time, by default. It's an added exercise for the reader, but you have to go into the settings of the extension and modify some of the mouse behavior. Basically if I want a link I click to share the same container as the parent, I C…

I add Containerize to that: https://addons.mozilla.org/en-US/firefox/addon/containerise It lets you define rules for URLs to allow any URL matching a pattern to always open in a certain container.

I tried using this but it doesn't preserve case so the regex matches don't work..

Doesn't seem to be very active either

I eventually moved to one of the fields that fixes the issue but have to install that from xpi

Re: Guide to Firefox Containers (2018)

#124
post #22

Earlier quoted context omitted.

this doesn't happen for me. what's the other add-ons you have ?

Fixed it. Containerise has a separate "Keep old tabs" setting that is different to the Multi-Account Containers "Replace tab" functionality. It works as intended now. Horray!

That's nice. thanks for sharing

Re: Guide to Firefox Containers (2018)

#125
post #120

Earlier quoted context omitted.

what you mention is one advantage, another example is that you are not limited to 2 contexts (private tab & non-private tab vs as many containers as you need). Related to the advantage you mention is also the reverse: clicking a non-facebook link from the facebook container can (if you want) open a non-facebook container

Ok starting to understand it. Seems like something I would have a hard time explaining to a non-tech person.

yes, you could describe that use case as "quarantining" websites in short, but I'd say it's a power user feature if managed manually.

If you install the "facebook container" extension, it's zero conf but it's only for facebook.

Another use case I saw users being interested in, is you have 2 (or more) accounts on a website and you can login in both at the same time in 2 separate containers (you cannot quarantine the website to the container in this use case because you need to open it in multiple containers). You can do that with incognito, but the second one is very temporary as closing the browser is going to log you out.

Re: Guide to Firefox Containers (2018)

#126
post #125

Earlier quoted context omitted.

Ok starting to understand it. Seems like something I would have a hard time explaining to a non-tech person.

yes, you could describe that use case as "quarantining" websites in short, but I'd say it's a power user feature if managed manually. If you install the "facebook container" extension, it's zero conf but it's only for facebook. Another use case I saw users being interested in, is you have 2 (or more) accounts on a website and you can login in both at the same time in 2 separate containers (you cannot quarantine the w…

So compared to a private tab, you basically get persistence and some form of organization (containers also act as groups).

How important is to have tabs from different containers in the same window?

Re: Guide to Firefox Containers (2018)

#128
post #8

Containers are great! But since the recent v.91 update screwed the tabs up so much, there's no quick visual way to scan and see which container-type each tab is. Great stuff, well done Mozilla! What's the point in being able to customise a container's appearance, including colour, if they're not described on the tab itself?

If you previously disabled the Proton redesign in about:config then you need to undo that setting. It no longer disables Proton, but it does interfere with the colored line that indicates which container each tab is a part of.

Re: Guide to Firefox Containers (2018)

#129

Earlier quoted context omitted.

I wrote up a quick email to friends/family at the beginning of the pandemic about Firefox containers in regards to the vaccine signups that were occurring. Since there was site isolation you could get as many “slots” as you were willing to solve capchas. Most of my friends and family were vaccinated because of this feature. A bunch say they use it now a days for normal site isolation but I did at least convert some p…

Wouldn't a private window achieve the same?

You would think but no. Open a private window and log into a site. Then open another and it’ll be logged in. Incognito windows share cookies. They are deleted once incognito mode is turned off but that doesn’t help us in our “open 100 windows at the same time to get a bunch of slots” use case here.

Re: Guide to Firefox Containers (2018)

#130

Earlier quoted context omitted.

Wouldn't a private window achieve the same?

You would think but no. Open a private window and log into a site. Then open another and it’ll be logged in. Incognito windows share cookies. They are deleted once incognito mode is turned off but that doesn’t help us in our “open 100 windows at the same time to get a bunch of slots” use case here.

Ah OK, I am coming from Safari background, where each private tab is isolated. Do you know why would Firefox make it differently by default?
Post reply on HN