Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

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 Mbohovái
  • 40 oguereko ko apañuãi
  • 17 Hecha
  • Mbohovái ipaháva alanbala

alanbala
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?

Opaite Mbohovái (3)

JeanAustinR
JeanAustinR
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.

Moambuepyre JeanAustinR rupive

earweed
earweed
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

alanbala
alanbala Porandu apoha
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.