1311845 - [Containers] Easier New Container Tab Experience

Status: NEW

(Core :: DOM: Security, enhancement, P3)

Description

[Robert (rrayborn, he/him)]

Containers is awesome, but I find it frustrating to create a new tab in a specific container.

The current workflow is to go through the menu or "Open Container Tab" icon.  Tanvi has informed me that you're also working on a long-press of the New Tab button to drop down some container options.

I would prefer one of the following solutions to any of the above:
 1) A pref to have new tab containers open with the same container group as the tab that currently has focus.  I think that it'd be fairly intuitive for a container to have the most-recently-used value unless you explicitly pick a "null" container.  I actually think that this would be a good default, but since it goes against the design decisions of the team, I'm suggesting a pref.
 2) A shortcut for opening a new Container with the same container group as the tab that currently has focus.

Any solution that requires you to hit a dropdown is too many clicks, too much mouse, and too much cognitive overhead IMO.

Thanks for such a cool feature

Comment 1

[Kamil Jozwiak [:kjozwiak]]

> 1) A pref to have new tab containers open with the same container group as
> the tab that currently has focus.  I think that it'd be fairly intuitive for
> a container to have the most-recently-used value unless you explicitly pick
> a "null" container.  I actually think that this would be a good default, but
> since it goes against the design decisions of the team, I'm suggesting a
> pref.

In bug#1325014, we've added the ability to create new tabs that will inherit the same userContextId of the current tab by middle/accel-clicking the new tab button "+". Example:

/ Personal Tab \/ Work Tab (active) \/ Banking Tab \

Middle/accel-clicking the "+" new tab button will result in the following:

/ Personal Tab  \/ Work Tab \/ New Work Tab (active) \/ Banking Tab \

>  2) A shortcut for opening a new Container with the same container group as
> the tab that currently has focus.

There's work being done in bug#1245262 that's looking into ways of creating a keyboard shortcut option that will open the  long press menu on the plus button that landed in bug#1272256.

Rob, do some of these solutions mitigate some of the frustrations of creating new container tabs? The container feature will also be in the next round of test pilot so the UI/UX might change depending on the feedback that we end up receiving from users.

Comment 2

[Bleddle]

Hello,

@Kamil

>In bug#1325014, we've added the ability to create new tabs that will inherit the same userContextId of the current tab by middle/accel-clicking the new tab button "+".

That doesn't work on Firefox 51.0.1 On a clean profile it just opens a new tab.

Personally, I would still prefer a pref/option to open new tabs (user initiated, not href or popups) in the current container. Not only would it not interfere with extensions that bind "middle click + +" to "open last closed tab", allow more customization.

If one were to go even further and that had access to a `newTab(url, container)` for extension development, one could envision an even more fine-grained handling of new tabs e.g popups not on the whitelist open in "Trash" container.

Cheers

Comment 3

[Firefox Bug Husbandry Bot]

Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020