Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Search bar behavior doesn't respect browser.search.openintab when clicked

  • 2 odgovora
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od naokiri

more options

What I want to do

Open new tab when searching from search bar

What I tried

Go to about:config, set browser.search.openintab to true

Version

Firefox 80.0.1 (64bit) on Windows 10

Steps to reproduce

  1. In about:config set browser.search.openintab to true.
  2. Open https://mozilla.org/ (Any non-search engine page will do.)
  3. Enter search query in the search bar
  4. Click the arrow in the search bar

Expected behavior

Open a new tab, searching with the query.

Actual behavior

Opens the search result page on the current tab.
What I want to do Open new tab when searching from search bar What I tried Go to about:config, set browser.search.openintab to true Version Firefox 80.0.1 (64bit) on Windows 10 Steps to reproduce # In about:config set browser.search.openintab to true. # Open https://mozilla.org/ (Any non-search engine page will do.) # Enter search query in the search bar # Click the arrow in the search bar Expected behavior Open a new tab, searching with the query. Actual behavior Opens the search result page on the current tab.

Izabrano rješenje

Yes, there is a bug on file for that. Firefox opens a new tab if you press the Enter key to submit the search from the Search Bar, but not if you click the button.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (2)

more options

Odabrano rješenje

Yes, there is a bug on file for that. Firefox opens a new tab if you press the Enter key to submit the search from the Search Bar, but not if you click the button.

more options

Thank you very much. I didn't notice there's another bug reporting system.

I think I don't have anything to add to that thread but I'll use there when it's clear that it's more a bug report rather than support question.

I hope they could fix the bug in near future.