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!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

New tab button behaviour should be updated to support new features

  • 1 antwurd
  • 1 hat dit probleem
  • 27 werjeftes
  • Lêste antwurd fan cor-el

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.

Alle antwurden (1)

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.

Bewurke troch cor-el op