291440 - window.open returns handler and closed is not set although popup has been blocked

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[André Hänsel]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0

The JS function window.open() returns a window handler and the "closed" 
property is not set although the new window has been closed (not opened) by the 
popup blocker.

Reproducible: Always

Steps to Reproduce:
1. Enable Popup blocker
2. Open a new window by executing JS "handler = window.open
('about:blank','test','');"
3. Check handler and its "closed" property

Actual Results:  
Handler is valid, closed is not set.

Expected Results:  
Depending on your view, the window has not been opened (handler should be 
false) or closed (handler.closed should be true).

Comment 1

[Peter van der Woude [:Peter6]]

could you provide a testcase please

Comment 2

[André Hänsel]

I added it as URL.

What I see is:
"Opening window, saving returned handler"
"handler: [object]"
"handler.closed: false"

What I expected is:
"Opening window, saving returned handler"
"handler: [object]"
"handler.closed: true"
or
"Opening window, saving returned handler"
"handler: null"

Comment 3

[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 4

[Peter van der Woude [:Peter6]]

can someone who understands this stuf check this one ?
setting NEW to prevent auto-resolve

Comment 5

[buovjaga]

(In reply to André Hänsel from comment #2)
> What I expected is:
> "Opening window, saving returned handler"
> "handler: [object]"
> "handler.closed: true"
> or
> "Opening window, saving returned handler"
> "handler: null"

The testcase now says handler: null when Firefox blocks the popup. As the result is expected, I will close this as WFM.

Arch Linux, FF 50.1.0