Open Bug 1646985 Opened 4 years ago Updated 10 months ago

"Select a container for each new tab" checkbox doesn't work with Ctrl-T

Categories

(Firefox :: Tabbed Browser, enhancement)

enhancement

Tracking

()

Tracking Status
firefox95 --- affected

People

(Reporter: nkharvey, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

Check the "Select a container for each new tab" under container tabs.
Press Ctrl-T

Actual results:

A new tab is opened without prompting for container.

Expected results:

A keyboard-accessible container prompt should appear, with the focus on the most frequently used container.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Tabbed Browser
Blocks: 1606265
Type: defect → enhancement
Version: 74 Branch → Trunk

Yes, this really is a problem when using containers. I can confirm this behaviour in 82.0.2.

still a problem in 2021 on 93.0

STR

  1. Open about:preferences#containers
  2. Check the "Select a container for each new tab" under container tabs.
  3. Press Ctrl-T
Status: UNCONFIRMED → NEW
Ever confirmed: true

Maybe related to this. But when that option is NOT checked then Ctrl+t works a bit unexpected also:

  1. Have a container tab open.
  2. Right click on the tab and choose "New Tab"
    Result: The new tab is opened in the same container.
  3. Press Ctrl+T
    Result: The new tab is opened without a container.

I guess Ctrl+T needs to be wired into the right action.

This was reported 3 years ago and still not fixed. Can this get assigned?

I keep coming back to try Firefox every couple of years but niggles like this keep driving me away

Duplicate of this bug: 1824528

How do we get eyes on this issue? such a simple but important QOL feature...my workflow heavily involves container tabs as I'm sure it does for many freelancers using Friefox (given we have to juggle multiple logins for the same sites)

You need to log in before you can comment on or make changes to this bug.