Javascript关闭浏览器窗口不弹出提示最新方法

作者: 李嘉日期: 2009-07-23 21:54

字体大小: 小中大

There is a hack for closing windows in IE without a warning. Although I've heard that it won't work for much longer.

<html>
<head>
<script>
function bye() {
self.opener = this;
self.close()
}
</script>
</head>
<body>
<a href="JavaScript: bye()">Bye bye</a>
</body>
</html>

An interesting trick but, it does not seem to work with the new XP SP2 or FF.
Although it may be the changes I just made to the Registry :D

注意：朋友说貌似这个方法在IE7&IE8中无效，经过我研究三个页面可以实现第二个页面自动关闭自己的功能，但不够完美，后续我会提供更完美的IE7&8 Hack方法。

--------------------------------------

I have an another idea.
Suppose, we have three web pages. (index.htm, index2.htm, pop.htm)

pop.htm : popup page.

index.htm : There we load a popup without any controllers, then redirecting parent window to index.htm.

index2.htm : On its UnLoad event it'll be redirected to itself.Also we can use an advertisement(s) here.

Problem seems to be little bit received.

But a new problem arises if we want to keep the popup being focused through its lifetime.After loading popup, and redirecting parent window, parent window will then focused.
How to keep popup focused all its life.

-------------------------------

For an internal, IE application, we use the following code to get rid of the parent window so we can open a new one without buttons and stuff:

function popViewer(currentWindow, mfSessionID, doSubmit) {
var windowName = buildWindowName(mfSessionID);
if(currentWindow.name == windowName){
currentWindow.focus();
if (doSubmit) {
document.body.style.cursor='wait';
process.submit();
}
}
else {
var newProcessURL = currentWindow.location.protocol + "//" + currentWindow.location.hostname + ":" + currentWindow.location.port + "/EnterpriseCommon/newprocesspageloader.jsp?windowname=" + windowName + "&origurl=" + escape(currentWindow.location);
var shell = new ActiveXObject("WScript.Shell");
shell.Run ("iexplore.exe " + newProcessURL, 7, false);
currentWindow.opener = null;
currentWindow.close();
}
}

We use the shell command so that we can start a new IE process because of some potential access violations we've seen when other windows have applets running. But you could just use a window.open to do the same thing. This, combined with a bunch of key code handling will minimize the opportunity for navigating in a way that wasn't intended. Of course, all of my users can still see my code.

Anyway, the reason I posted this is to point out that this works in XP SP2. Well... at least it does for me. :) ...and it seems like something that might come in handy for anyone building an internal application.

Hope this helps someone.