Default container names specific to a browser window

[Dannyzen]

Hi there,
I'm a big fan of the profiles functionality in firefox. Containers look like they support the use case I'm looking for in a modern way. My use case is pretty simple: I have multiple accounts on account specific sites (azure, aws, google, etc.) I use these services for both work and home. I use different browser windows to hold work accounts and home accounts.

This feature request is to be able to have Firefox open a specific container (as its default) in a browser window so that my sessions can be segmented and support a "this window has home tabs" and "this window has work tabs" workflow

[lmorchard]

Yeah, this is my workflow too. Making tab-by-tab container decisions is a lot of mental overhead, IMO.

I basically segment my contexts with windows. Or a window in another browser if I need to separate logins (e.g. on Google). Or a private window if I want a disposable context. I'd also love to be able to naturally move tabs between two different windows to switch containers. And when I hide a container, I'd want restoring it to try to restore the original window arrangement - not pile all the tabs into one window.

[janbuchar]

This would help my workflow a lot! It would also be great if the container name could be added to the window title - this way, I could handle each container differently in my WM.

[AWOL-TECH]

I would like to add an infinite amount of +1s to this !

I'm a user of Multifox (or was) with the "window mode" option enabled , as its no longer supported I can no longer assign a profile to an entire window, my workflow is similar to the previous posters.

Setting profiles on a per tab basis does not work for me as I can have anywhere upto and over 170odd tabs across several windows.

Being able to set a profile per window (or even option to have it per window or per tab to appease everyone) would be a massive advantage and would definitely help to streamline a very busy work flow !

[jonathanKingston]

To implement this we would likely need a platform change to do this cleanly. Other extensions have been able to implement this however I would rather not make hacks.

See: https://bugzilla.mozilla.org/show_bug.cgi?id=1403422

[Dannyzen]

Thanks @jonathanKingston for the context. What's the likelihood that we might expect this feature from the core mozilla team in the near future?

[jonathanKingston]

Not sure, "container windows" is certainly well asked for and this is essentially that somewhat. I think we should keep pushing for the platform support for this feature first. Even if we don't end up making it an option it will allow addons to make this much more cleanly.

[groovecoder]

Note: this is also a commonly-mentioned feature for Chrome-like parity to help users switch from Chrome. ;)

[AWOL-TECH]

In addition to the note from @groovecoder - it will also help to stop users switching over to chrome now that there is currently no easy way to set container windows with Firefox anymore, it may not seem like much but it is a deal breaker for many users

[Dannyzen]

If I'm reading @jonathanKingston right, there's a higher likelihood the extendability will be built out before this becomes a first class feature, resulting in an opportunity for an extension to add the feature.

If this is the case, I'd be happy to put a bounty on the extension and ask if the others on this issue would be interested in joining me.

[AWOL-TECH]

Unfortunately extension programming isn't something I've done before, but I do build websites, I'd be happy to build a site, possibly even host it too, if a project was started to cover the container windows feature.

[sandinmyjoints]

This and container-scoped bookmarks are the only things keeping me from switching entirely to Firefox -- hope it happens soon!

[gustafbstromuu]

I would definitely love if I could set a default container – this is would enhance the Firefox browsing experience by some order of magnitude!

[DHager]

@sandinmyjoints I too want both of those things (bookmarks and window-defaults) but we should probably consider the scenario where they conflict.

In particular, when someone uses a Container-X-by-default window, and selects a Container-Y bookmark.

Personally, I think the bookmark's settings should win, it's the "privacy safest" outcome. If someone's workflow is to use the same bookmark in multiple identities, then it's probably best for them to not set a specific container for that bookmark at all.

[chicagobuss]

Happy new year, all. Any news on this effort? Really liking containers but wish I could configure a default for windows (and a default container overall) - when I click links in slack for work it's very annoying that they don't open in the work container!!

[DHager]

OK, so it sounds like we're up to four related mechanisms:

1. Domain-based (in Firefox 57)
2. Bookmark-based (in Firefox 59)
3. Window-based (?)
4. Global default (?)

@chicagobuss While it would be great to set a "Work" container a the default for external links when on an actual at-the-office desktop, I have a harder time imagining the "right" behavior for a multipurpose machine. Firefox can't know whether the link you clicked was from a work-conversation versus a personal-one.

[sandinmyjoints]

@DHager re: default-container windows and bookmarks colliding: I'd prefer to see container-bound windows, in which it is not possible to open a tab that uses a different container. One (or more) window(s) for Work containers only, others for Personal, etc. Then bookmark conflicts go away because you can only see/navigate to bookmarks associated with container bound to the currently active window.

This is what I'm used to in Chrome, so I'm very comfortable with this and my bookmarks are organized according to this principle. I can imagine use cases where you want to have tabs from different containers next to each other in the same window, like comparing a work account with a personal account for some reason. I'm sure there are creative ways to accommodate that use case.

[joesanford]

What about, instead of setting the context of a window, the functionality is mirrored in another way? For instance, like opening a link in a new tab from a container that stays in a container, also having this occur when opening a new tab from a container? Is this more feasible in the framework?

[soar]

Window-based behavior should be great enhancement! Will wait for it!

[th3coop]

+1. I'm constantly opening "generic" tabs in the window I've designated for [personal | work | other] account. I've only been using this tool for about 20 minutes and I already reeeeeally really want this :)

[DHager]

@sandinmyjoints @joesanford What if instead of some mechanism for explicitly assigning a Window-Container relationship, it becomes implicit based on the population of tabs already present inside that window?

Suppose the user creates a tab with ctrl-t, which always happens in the context of a particular window. Check if that window exclusively contains tabs bound to a single container X. If so, then it is safe to assume that the user wants another tab for the container X as well. If not, then fall back to the current behavior.

In other words, you create a "Work Window" simply by making sure that none of the tabs in it are anything except Work tabs, and after that Firefox helps you avoid accidentally breaking that pattern.

[digitalowlnyc]

@DHager @sandinmyjoints @joesanford

What if instead of some mechanism for explicitly assigning a Window-Container relationship, it becomes implicit based on the population of tabs already present inside that window?

Interesting proposal, it seems like there are at least three cases here:

1. when a user clicks a link outside of the browser with no context available
2. when a user clicks a link inside an existing tab.
3. when a user clicks a bookmark

For case no. 1, what about simplifying and just using the last focused container (or window)? I personally think any implicit workflows should be as simple as possible for a user to easily reason about what will happen. This solution goes along with user workflow IMO, because typically I am already looking at a "work" tab whenever I am clicking links in other programs related to work. I can live with the compromise of accidentally clicking a link meant for personal and having it open in my work tab, or vice versa. This solution can potentially be applied to no. 3 as well.

For case no. 2, it seems like what makes sense is to stick to the same container for any clicked links.

In general, I like the "one container per window" approach as it seems like it would simplify user workflows.

I have been a Chrome user the past 4-5 years and would love to make the switch back to Firefox - this is the one thing holding me back. I am a developer and am open to being involved with development on this (in FF or a plugin) as a way to pitch in and give back to the FF community.

[th3coop]

+1 on @digitalowlnyc comment. The 3 contexts and how they are handled as well as helping out. I'm a Dev as well.

I don't think windows should be implicitly assigned an accnt though. A window should be opened under a specific accnt. Any tab opened in that window opens with that accounts settings. The window has it's assigned colour and it's icon so I know which window is which.

Again, if it's feasible to parcel out tasks I'd love to help out. I guess I could just look at the source.

[DHager]

@digitalowlnyc

Interesting proposal, it seems like there are at least three cases here:

Adding two more:

• Case 4: User creates an URL-less tab in an existing window (e.g. ctrl-t) and wants it to already be for a certain container.
• Case 5: User creates an URL-less tab in a fresh window (e.g. ctrl-n) and wants it to already be for a certain container.

I find Case 4 is especially common when the next thing I'm about to do is type in some web-search terms.

[th3coop]

Case 4: User creates an URL-less tab in an existing window (e.g. ctrl-t) and wants it to already be for a certain container.

This was the use case that made me go back to Chrome. I was constantly opening a "session less" tab.

[tom-james-watson]

Yeh I'd also point out that I ended up stopping using that Sticky Containers because it had a few annoying bugs. If I remember correctly it made reopening of closed tabs work in strange ways. Would be far better to have this built into the browser itself.

[grnassar]

Also having some issues with Sticky Containers, and hoping that that functionality finds its way here -- and even better if (as in @tom-james-watson 's comment 4 above this one) either made the default or could be configured to be default in options.

[andrewleech]

Not as comprehensive as Sticky Containers was, but https://addons.mozilla.org/en-US/firefox/addon/sticky-window-containers/ does a similar thing.
Whatever container the first tab it in, any new tabs open in the same container.

[tom-james-watson]

That actually works far better than Sticky Containers - thanks!

It's a shame there doesn't seem to be any first-party activity on addressing this.

[Snogren]

Thanks @andrewleech! Works for me.

[adamshand]

I also really want this feature for the same reason. I'm a freelancer so sometimes have windows open for half a dozen different clients all logged into similar sites. Containers are great but it's annoying to have to constantly right click "reopen tabs in container" and it's easy to make mistakes and end up logged in as the wrong user. I also manage this by having a window per client.

Thanks for the recommendation for sticky window containers, that a big improvement!

[grnassar]

Not as comprehensive as Sticky Containers was, but https://addons.mozilla.org/en-US/firefox/addon/sticky-window-containers/ does a similar thing.
Whatever container the first tab it in, any new tabs open in the same container.

That is a huge improvement over stock. Thank you!

[githubflub]

Hello???

[moontails]

happy to work on this :)

[michalfita]

I didn't care that much but I moved jobs where Google is now the productivity suite with everything in the browser. Keeping the stuff separated by the Window would help a lot. A function sending a tab opened in default work windows into a private window would help as well.

[michalfita]

I didn't care that much but I moved jobs where Google is now the productivity suite with everything in the browser. Keeping the stuff separated by the Window would help a lot. A function sending a tab opened in default work windows into a private window would help as well. Sticky Windows Containers tries to address this problem, but it's not good enough especially for dealing with where tabs are open from requests coming from outside the browser.

[nemothorx]

containers have become one of the killer features for me in FF, and I've spruiked it to several colleagues successfully.

But I wanted more. I wanted different windows to have different default containers. This seems to be the thread to voice my support for this type of functionality!

I do notice a lot of people want windows to be limited to a single container - that wouldn't work for me. By and large I rely on being able to mix containers within a window.

My ideal (so I imagine) case would simply to be able to configure a window as having a default container, which applies to new tabs when created interactively ([New tab] menu item, or equivalent hotkey)

I still want new tabs within other containers to be possible. I'd also want links opened from external applications to default to the default session.

[achernyakevich-sc]

I could advise to try Simple Tab Groups add-on. In my case it resolve my problem and works not only for window:

https://addons.mozilla.org/en-US/firefox/addon/simple-tab-groups/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

In few words: you could define in setting that the Container C-A should be always open in the Group G-A and as soon as Group G-A is open in separate windows then new tab that should belong to C-A Container will open there.

In case of you wish to open new tab using the same container as current tab then I would advise to vote to introduce Ctrl+Shift+0 shortcut in the #462 (comment) :)

[r-0-0-t]

+1 for this feature

[grahamperrin]

Please use the upvote feature. (Not written +1)

[grnassar]

In case of you wish to open new tab using the same container as current tab then I would advise to vote to introduce Ctrl+Shift+0 shortcut in the #462 (comment) :)

Unfortunately doesn't cover the use cases that a lot of previous posters have mentioned. New tab creates in same container as current tab isn't the desired result -- it's new tab creates in some defined default container, whether the current tab is in that container or not. (Otherwise, people like @nemothorx above wouldn't find it suitable, as they are working with multiple containers in a window. I do the same. Note that this is different from having a window locked to a single container -- I think at most very few really badly want that, as there are already add-ons that get very close to that functionality like Sticky Containers mentioned previously.)

[achernyakevich-sc]

In case of you wish to open new tab using the same container as current tab then I would advise to vote to introduce Ctrl+Shift+0 shortcut in the #462 (comment) :)

Unfortunately doesn't cover the use cases that a lot of previous posters have mentioned. New tab creates in same container as current tab isn't the desired result -- it's new tab creates in some defined default container, whether the current tab is in that container or not. (Otherwise, people like @nemothorx above wouldn't find it suitable, as they are working with multiple containers in a window. I do the same. Note that this is different from having a window locked to a single container -- I think at most very few really badly want that, as there are already add-ons that get very close to that functionality like Sticky Containers mentioned previously.)

@grnassar Ctrl+Shift+0 is not a silver bullet and thing that will fix your workflow. It is convenient addition to solution by using Simple Tab Groups (STG) add-on. STG provides you a possibility to organize some group, define explicitly that all new tabs in this group should be open in some container and having open this group in the separate window you will achieve what you expect.

As well STG has some other feature that cold be helpful. E.g. you could configure that opening some link in dedicated container will automatically move tab to the related tab group (and in your case window).

In reality, Multi-Account Containers (MAC) is more about container management but not about tabs and windows. So it is reasonable to use special add-ons to handle tabs/windows functionality (that do it great way) than expect that MAC will get implemented similar. :)

[julie777]

I'm going to add my 2 cents to a complicated issue. I believe that part of the problem is the conflation of tab groups and tab containers.

A window is an implicit group of tabs. Some people use one window for work stuff and one for personal stuff.
Simple tab groups provides explicit groups of tabs. I have one for development, one for a specific project I am working on, etc.
Many of the discussions that I have seen in the multi-account-containers issues have more to do with tab groups that with tab containers.

A group of tabs provides an environment for working on a specific task by keeping all the related tabs together.
This is efficiency issue.

A tab container has the purpose of keeping the contents (metadata, such as cookies, etc.) of the tabs in that container from being accessible from tabs outside that container. The perfect example is the facebook container and the great choice of a fence as its icon. Facebook wants to track everything you do online and the facebook container stops that.
This is a security issue.

Sadly tab containers don't easily support collecting all the tabs logged in to a site with the same account, and keeping them separate from tabs logged into the same site from another account.

While I use and appreciate both simple tab groups and tab containers, neither truly provides a complete solution to the individual problems and they definitely don't work together an overall solution to make what everyone seems to be asking for simple and efficient.

[achernyakevich-sc]

While I use and appreciate both simple tab groups and tab containers, neither truly provides a complete solution to the individual problems and they definitely don't work together an overall solution to make what everyone seems to be asking for simple and efficient.

I use both at the same time - MAC + STG. And it works perfect because STG knows about MAC existence and can be configured any way you would like it should work. But I agree that user should configured it as he needs and there will be no one "silver bullet" configuration that will match to all possible usage scenarios. It is like philosophy law - if you have universal solution then you will pay something for this universality - either performance or efforts for sharp tuning and configuration. :)

[ejdiener]

I know I'm years late to the party, but want to again bring this up! It would be so helpful if I could have a default tab type set for each window.