Cari Bantuan

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

window.open is not supported by 40.0.+ (39.0.0 and below do), can this please be fixed?

  • 5 balas
  • 3 memiliki masalah ini
  • 3 kunjungan
  • Balasan terakhir oleh FredMcD

more options

I often visit web sites that will, when a link is clicked or an action takes place, a new browser window will appear with the content of the URL or the desired action (such as when paying a bill there is redirect to another vendor who then handles the transaction). A couple of days ago, I tried to pay a bill and Firefox gave me a blank window but inspecting it via "command-u" shows that HTML is there. When I did it through Safari it worked. Today I wanted to get to a ProQuest database through a link provided by UCLA's library and I got the same result: a blank window with HTML code showing up when "command-u" is used. Surprisingly, pasting the link in a new browser window did produce the content. But the original blank browser window would not display anything even if it is re-loaded. Both of the actions I describe are produced by scripts at these two very different sites but the response of Firefox is the same: a blank browser window.

To isolate it, I tried the simplest: I used window.open in my work web site to send the visitor to the original publisher of my work. An example of such approach is the following snippet:

<a href="http://link.aps.org/abstract/PRL/v72/p1658"

    onclick="window.open(this.href);return false">original publication</a>.

Clicking on the link used to open a new browser window at aps.org.

But now it does not do this after upgrading to 40.0.+ (currently at 40.0.3).

This is, as far as I know, a "supported" HTML call. And it works for 39.0.0 down to 34.0.5 (could have gone furtherback but I did not see the point).

I think this is a major flaw with 40.0.+ and needs to be fixed as soon as possible.

Thank you for reading this far.

(This post was made from a Mac Pro [Xeon], kept at 10.6.8 for complicated reasons. But the results are identical under 10.10.3 elsewhere.)

I often visit web sites that will, when a link is clicked or an action takes place, a new browser window will appear with the content of the URL or the desired action (such as when paying a bill there is redirect to another vendor who then handles the transaction). A couple of days ago, I tried to pay a bill and Firefox gave me a blank window but inspecting it via "command-u" shows that HTML is there. When I did it through Safari it worked. Today I wanted to get to a ProQuest database through a link provided by UCLA's library and I got the same result: a blank window with HTML code showing up when "command-u" is used. Surprisingly, pasting the link in a new browser window did produce the content. But the original blank browser window would not display anything even if it is re-loaded. Both of the actions I describe are produced by scripts at these two very different sites but the response of Firefox is the same: a blank browser window. To isolate it, I tried the simplest: I used window.open in my work web site to send the visitor to the original publisher of my work. An example of such approach is the following snippet: <a href="http://link.aps.org/abstract/PRL/v72/p1658" onclick="window.open(this.href);return false">original publication</a>. Clicking on the link used to open a new browser window at aps.org. But now it does not do this after upgrading to 40.0.+ (currently at 40.0.3). This is, as far as I know, a "supported" HTML call. And it works for 39.0.0 down to 34.0.5 (could have gone furtherback but I did not see the point). I think this is a major flaw with 40.0.+ and needs to be fixed as soon as possible. Thank you for reading this far. (This post was made from a Mac Pro [Xeon], kept at 10.6.8 for complicated reasons. But the results are identical under 10.10.3 elsewhere.)

Solusi terpilih

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


In the address bar, type about:preferences#content<enter> Look for Block pop-up windows. To its right, press Exceptions.

Do the same for any blocking programs / add-ons.

Baca jawaban ini dalam konteks 👍 1

Semua Balasan (5)

more options

Solusi Terpilih

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


In the address bar, type about:preferences#content<enter> Look for Block pop-up windows. To its right, press Exceptions.

Do the same for any blocking programs / add-ons.

more options

FredMcD, thank you very much for the valuable suggestion.

I did start Firefox with the add-ons disabled and that did solve the problem.

I then proceeded to trouble-shoot the issue by enabling my add-ons one by one until the one causing the problem was identified: it is ghostery 5.4.7.

It appears that this problem is known in the ghostery community. Unfortunately, none of the reporters seems to be familiar with how new browser windows "pop": it is via a call to windows.open. Thus, they could not identify where the incompatibility with Firefox 40.0.+ was. I have now reported it in their web pages. Hopefully, it will be patched soon. (Interestingly, such a problem is not present in ghostery 5.4.7 for Safari. Most likely due to architecture?)

The problem is therefore solved by turning off ghostery. Alternatively, ghostery can be downgraded to the previous version (5.4.6.1) available at

https://addons.mozilla.org/en-us/firefox/addon/ghostery/versions/?page=1#version-5.4.6.1

(I tried to see if it was a pop-up blocking issue before posting. It wasn't.)

Again, thank you for pointing the way. Much appreciated.

more options

That was very good work. Well Done.

more options

The least I could do after your very helpful tip (as well as the non-judgemental manner in which it was delivered!).

Henceforth, I will use this approach when Firefox (or any other app with add-ons) misbehaves. (BTW, I think it is a misnomer to call this approach "safe mode." It is better, I think, to call it "native" but I realize it is a verbiage legacy issue related to Windows usage. Oh, well.)

more options

Very good. And never be afraid to ask ask questions.