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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Private Window doesn't allow multiple windows open

  • 8 àwọn èsì
  • 1 ní ìṣòro yìí
  • 16 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ IBTrey001

more options

Hi,

I'm trying to develop something in my localhost site. To cross the T's and dot the I's I'm testing it in a private window and for the first time, it doesn't like it.

I can open the first pop up, but I use multiple window.opens with unique window names to create multiple popups. When I get to my second popup that I'm trying to test, it comes up with the "Firefox Developer Edition prevented this site from opening a pop-up window" message with the options button in the top right. Clicking this and going to "Edit pop-up Blocker Options" takes me to that allowed sites window.

I've added my site in 3 ways:

http://localhost http://mydomain.local http://127.0.0.1

and still Firefox Developer Edition (in private mode only) blocks the popup.

Any ideas of what I can do to help fix it?

Hi, I'm trying to develop something in my localhost site. To cross the T's and dot the I's I'm testing it in a private window and for the first time, it doesn't like it. I can open the first pop up, but I use multiple window.opens with unique window names to create multiple popups. When I get to my second popup that I'm trying to test, it comes up with the "Firefox Developer Edition prevented this site from opening a pop-up window" message with the options button in the top right. Clicking this and going to "Edit pop-up Blocker Options" takes me to that allowed sites window. I've added my site in 3 ways: http://localhost http://mydomain.local http://127.0.0.1 and still Firefox Developer Edition (in private mode only) blocks the popup. Any ideas of what I can do to help fix it?

All Replies (8)

more options

Could you try adding the exception through the Permissions panel of the Page Info dialog. While you are on the page that is going to call window.open() and before you trigger it, you can call up the dialog using any of these:

  • right-click a blank area of the page and choose View Page Info > Permissions
  • (menu bar) Tools menu > Page Info > Permissions
  • click the padlock or "i" icon to the left of the site address, then the ">" icon, then More Information > Permissions

Scroll down to "Open Pop-up Windows" and uncheck the "Use default" box, and then select the Allow permission.

There's no Save button in this dialog, it should be saved in real time as you make changes. However, I'm not sure everything is retained once your private session ends.

more options

Hi Jscher,

I went to the page and it's already unticked. :S

more options

Perhaps this is a new issue with using specific named windows. I assume using "_blank" doesn't cause this problem?

more options

I think it is new - I was able to do this earlier this week and it was updated.. yesterday? or maybe the day before so might be new bug introduced then

I haven't tested _blank yet

more options

Does it make a difference whether multi-process is enabled or disabled?

  • browser.tabs.remote.autostart.2 = true/false
more options

I tried changing the setting to no avail :(

more options

Does it work if you allow all pop-ups?

more options

yes, I've allowed pop-ups and added the domain / ips to allowed sites to no avail