본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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

  • 2 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: 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.

선택된 해결법

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.

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (2)

more options

선택된 해결법

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.