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!

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

Mozilla 도움말 검색

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

자세히 살펴보기

When I open a new window, it opens behind the exist ing window instead of in front of it. How can I fix this?

  • 3 답장
  • 40 이 문제를 만남
  • 17 보기
  • 최종 답변자: alanbala

more options

When I click on a link and I choose the option to open link in a new window, it opens behind the currently open window instead of in front of it. This is a real nuisance. Why is this happening, and how do I fix it?

When I click on a link and I choose the option to open link in a new window, it opens behind the currently open window instead of in front of it. This is a real nuisance. Why is this happening, and how do I fix it?

모든 댓글 (3)

more options

Hi alanbala,

There are several possible reasons why the new window opens in the background and not in the foreground by default.

  1. another installed program is causing this
  2. the Firefox main window is set to Always on Top
  3. probably a Windows 7 bug
  4. possibly a Firefox bug https://bugzilla.mozilla.org/show_bug.cgi?id=790013

What you can do is

  1. update your Windows 7 to the latest security patches
  2. open Mozilla Firefox in Safe Mode (see KB article Diagnose Firefox issues using Troubleshoot Mode)
  3. evaluate the other programs installed on your computer
  4. open new links on a new tab

Let us know your progress. I will be following this support thread.

글쓴이 JeanAustinR 수정일시

more options

Go to Tools>Options>Tabs When I open a new link switch to it immediately>>checking this brings new tabbed page to front automatically

more options

I have had the correct Tools/Options boxes checked from the very beginning, but it makes absolutely no difference. The issue began happening after a prior Firefox update, probably almost two years ago by now, so I don't remember which one.