Randy Webb wrote :
Gérard Talbot said the following on 9/1/2005 12:54 PM:
Randy Webb wrote :
ewosch said the following on 9/1/2005 3:44 AM:
This alert occurs only if there is only one window and cannot be
switched off.
That is far from the truth.
It does work if there are more than one window.
It *can* be switched off.
That's is already mentioned in MSDN documentation too.
Where?
"Using script to close the last running instance of Microsoft Internet
Explorer also opens the confirmation dialog box."
http://msdn.microsoft.com/workshop/a...asp?frame=true
People way over-want to kill opener windows but this goes against the
best
interests of the users.
That depends on the user I guess.
I make a general rule, a generalization if you prefer, from this.
Any/every window has a system command close [x] button on the titlebar.
So why do scripters need to provide me with links, buttons, etc.. to
close that window. If I can open a new window on my own, I certainly can
close a secondary window on my own. Same thing with closing the internet
connection, shutting down the PC, closing the tv, etc.. I do not need
any additional, extra help in managing (open, resize, move and close)
windows which should be under my complete and entire control to begin
with. Browser manufacturers (Mozilla, Opera, Microsoft, Safari,
Konqueror, etc) understand such perspective and agree with it and they
are providing users with veto powers over script methods like open(),
resizeTo, moveTo, resizeBy, resizeTo, close, etc..
Expect MSIE 7 to put an end to all this (wink) and expect your scripts
to fail closing such IE 7 windows.
Somehow, I doubt it but would be totally shocked if it does. Considering
that IE has had that bug since IE5 or so, and it hasn't been fixed
through 3 versions, I don't see them fixing it now. That would require
MS to admit they had flawed software and actually fix it.
They can fix the bug without admitting anything seriously detrimental
too; security is a concern for all browser manufacturers and for
web-aware software makers. I created a page back 1-2 years ago with your
own data, Randy:
http://www.gtalbot.org/BrowserBugsSe...penedByJS.html
and then posted a request (see/search for: "opener property should be a
read-only property") in that sense at:
http://channel9.msdn.com/wiki/defaul...plorerSecurity
I also made sure Opera dev. is aware of this close() issue.
Mozilla-based browsers already deny the capability to close such
windows;
Don't bet on it.
Current Mozilla-based browsers do deny the capability to close such windows.
The default setting of dom.allow_scripts_to_close_windows in
about
:config is false.
reasonable and responsible web designers don't try to close
non-script-initiated windows.
"reasonable and responsible web designers" don't use secondary windows,
so they have no need to close superficial windows.....
I would add one nuance to such statement but I'd rather not since I
fully (general rule) support this opinion.
Gérard
--
remove blah to email me
