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

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

  • 2 odgovori
  • 1 ima ovaj problem
  • 1 view
  • Posljednji odgovor poslao 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čitajte ovaj odgovor sa objašnjenjem 👍 0

All Replies (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.