We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

New tab button behaviour should be updated to support new features

  • 1 reply
  • 1 has this problem
  • 27 views
  • Last reply by cor-el

Ch Ex Mo
Ch Ex Mo
more options

As long as Firefox has added the containers feature in the last updates, the actual behavior of the new tab button needs to be updated, or at least configurable. If you're in a specific container, new tab opens a no-container tab. I believe this should be the actual container of the active tab, instead of a no-container.

As long as Firefox has added the containers feature in the last updates, the actual behavior of the new tab button needs to be updated, or at least configurable. If you're in a specific container, new tab opens a no-container tab. I believe this should be the actual container of the active tab, instead of a no-container.

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

There is a pref to open the container menu via a left-click.

  • privacy.userContext.newTabContainerOnLeftClick.enabled = false

Otherwise you can open the container menu via a long left-click or a right-click.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

Modified by cor-el