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).
could you provide a testcase please
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"
can someone who understands this stuf check this one ? setting NEW to prevent auto-resolve
Status: UNCONFIRMED → NEW
Ever confirmed: true
(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
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.