javascript:self.close() doesn't close the browser window.

RESOLVED INVALID

Status

()

--
minor
RESOLVED INVALID
16 years ago
16 years ago

People

(Reporter: niklas_bolmdahl, Assigned: security-bugs)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021115
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021115

javascript:self.close() doesn't close the browser window. The javascript works
w/ IE & Opera. It has worked on earlier Mozilla builds. 
(
http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2b/mozilla-win32-1.2b-installer.exe
)

I encounter the problem when I log out of a swedish community called
"Lunarstorm". The log-out process is supposed to close the window, but it
doesn't. (the link to the log-out process is:
http://www.lunarstorm.se/ciao.asp?status=close )


Reproducible: Always

Steps to Reproduce:
1.setup doesn't seem to matter
2.I point my browser to http://www.lunarstorm.se/ciao.asp?status=close (usually
through a link, although it doesn't matter in this case)
3.I click the right link, which says "close this window" in swedish

Actual Results:  
Nothing happens.

Expected Results:  
The browser window should close, but it won't work.
I believe we're supposed to be putting up a dialog asking for permission to
close (since the window was not opened by script).  Instead we're silently
ignoring the call.
Assignee: jst → mstoltz
Status: UNCONFIRMED → NEW
Component: DOM Level 0 → Security: General
Ever confirmed: true
OS: Windows XP → All
QA Contact: desale → bsharma
Hardware: PC → All

Comment 2

16 years ago
Silently ignoring the call is the correct behavior.

Comment 3

16 years ago
I belive this is invalid/wontfix since bug 32571 is about not allowing this
behaviour.
Ah, indeed.  Looks like we decided on no dialog.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.