189237 - Popup blocking affects new windows opened by flash

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Francisco León]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030110
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030110

I have "open unrequested windows" turned off and the website can't open the new
window when clicking the right blue button on the main page.

Turning on the option makes it work. Since i am clicking on the button, it
should allow to open the new window with the option turned off, right?

Reproducible: Always

Steps to Reproduce:
1.Go to site and click button with the open unrequested option off
2.
3.

Actual Results:  
Nothing

Expected Results:  
Open new window

Comment 1

[Phil Schwartau]

Not JS Engine; reassigning to Browser-General for more information.


> when clicking the right blue button on the main page.

Francisco: do you mean the "Eidos" button at the top-right of
http://www.ionstorm.com/news/informant/ ?

That's the button I was trying. The new window came up even if
I had "open unrequested windows" turned off.

I am using Mozilla trunk binary 2003011708 on WinNT. 

Comment 2

[Francisco León]

No, go the page specified above, click on the UK flag then 2 blue buttons will 
appear, choose the right one (pc)

It does not do anything with open unrequested windows off.

Comment 3

[Gervase Markham [:gerv]]

This is the antithesis of bug 176079.

Gerv

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

Please reopen if you can reproduce in current SeaMonkey2 builds (and then it probably should go to Core or Toolkit), but unless this can be reproduced, I'll mark it INCOMPLETE for now.