264182 - Popup-windows called from Java-applet blocked.

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Thanh Nguyen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040927
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040927

Popup-window called/requested from Java-applet (by click a button on the applet)
blocked, if users block unrequested popup-windows (in
Edit->Preferences->Privacy&Security->Popup Windows).

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
Popup-windows called/requested from Java-applet by users should not be blocked.

I am using Mozilla 1.8 Alpha 4.

Comment 1

[Daniel Veditz [:dveditz] (OOO: back Aug 26)]

Not a security bug.

Not enough info. Please read the bug writing guidelines on how to including
enough information so that we can resolve the problem. On the surface it would
appear that if the user has said "no popups" then not getting popups would be
the right behavior. Hard to say without a specific example, but my guess is that
this Java applet is using calls out to the browser via Javascript and thus this
would be correct behavior. You can always whitelist the site in question, as
always with popup blocking.

Comment 2

[Thanh Nguyen]

Dear!

//From Mozilla
On the surface it would
appear that if the user has said "no popups" then
not getting popups would be
the right behavior.

//From lmdtnn
I think that is not the correct behavior. You
should mean "no popups" as "no unrequested popups".
You may try this by making a simple example.

//From Mozilla
Hard to say without a specific
example, but my guess is that
this Java applet is using calls out to the browser
via Javascript.

//From lmdtnn
You are right about your guess.

This bug refers only to Mozilla 1.8 Alpha 4. The other
versions of Mozilla work OK in this connection.

Thank you for your help/reply.

Regards, Thanh Nguyen


(In reply to comment #1)
> Not a security bug.
> 
> Not enough info. Please read the bug writing guidelines on how to including
> enough information so that we can resolve the problem. On the surface it would
> appear that if the user has said "no popups" then not getting popups would be
> the right behavior. Hard to say without a specific example, but my guess is that
> this Java applet is using calls out to the browser via Javascript and thus this
> would be correct behavior. You can always whitelist the site in question, as
> always with popup blocking.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Didn't we special-case something to allow plugins to open windows if they use
the proper plugin api calls to do so?

Comment 4

[Scott]

I am running FF 1.0 on a Win Xp machine no extension or theme’s installed. When
I am playing games on Pogo.com and click links on the screen the FF popup
blocker does not allow these windows to open, however I do want these windows to
open. So I click the yellow bar for popup blocker options. And I set it to allow
popup’s for “xxx.pogo.com” however when I click the same link again the popup
blocker will not allow the window to open. I have tried this with various games
on Pogo.com and I get the same result. Would this have anything to do with the
fact that the screen in question use’s Java? Also tried clearing my cache,
history, and cookies still same result.  

to reproduce goto www.pogo.com pick any game for example "word whomp" click the
play game button (will need to create an account free of charge). Once the java
applet loads on the left side of the screen you will see a button that says
"cash in" click this button and FF will block this popup.  Click to allow popup
and click the link FF will still block the Popup.  

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.