Hello Experts
I have a parent window where i have table with 100 rows of images.
when i click any image a pop up window opens.
when i click submit button in the child window to close the window
,focus should go on same image of parent window
Actually it goes to the first index value
I am looking to get focus back on the same page and location from where it has posted
please help me out in getting some solution
regards
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
hmm, only if your timing is lucky. once the window is closed it doesn't execute code anymore. In the code below, you will either get the alert, or the window will close -- but not both:
<HTML>
<HEAD>
<SCRIPT language="javascript">
function test()
{
self.close();
for ( var i=0,n=500,x=0; i<n; i++ )
x += i;
alert(x);
}
</SCRIPT>
<BODY>
<A href="#" onclick="test();return false;">test</a>
</BODY>
</HTML>
You're right with the alert, but even if I loop for a million (literally) the window will not close until the loop is complete because the browser will not do anything until the JavaScript is complete (like I said). The exception to that is alerts (and confirms, etc). They are the only thing that interrupt JavaScript's execution to allow the browser to do anything (including updating the GUI or closing):
==========================
function runTest()
{
self.close();
for(var i = 0; i < 1000000; i++)
continue;
window.opener.focus();
}
>> If you pass the id of the image clicked to the child window, and then when closing it, use this id as an argument in a call to a function, you can have this function setting the focus.
Assuming you know which window. You can't just do document.getElementById from any window, it has to be the correct document. He'd need to pass a whole array of window references if he's got more than 1 window open and wanted to know which was called. OR he could have them stored on the parent and call a function from the parent to call a function on a previously stored array. It really depends what he has/needs. So "gamequestions", what's the situation?
>> The exception to that is alerts (and confirms, etc).
you can't submit a form either -- this doesn't work:
function runTest()
{
self.close();
for(var i = 0; i < 1000000; i++)
continue;
document.myform.submit();
}
What you may be seeing is that focus just naturally goes back to the parent when the popup closes -- or that you are getting lucky on timing.
Anyway, not to belabor that point to much -- I think the problem here has to do with what the submit button is doing. GameQuestions -- can you post the code you are using for this?
>> What you may be seeing is that focus just naturally goes back to the parent when the popup closes
Nope, I made sure I had another window on top of the one that focusses. I wish I could find the MSDN article again (and I'll post it as soon as I can).
Regarding the submit situation: when you submit the form, the submit is actually taking place (thus the end of the JavaScript). The browser then calls the close() and then the submit() on its own in its own thread. Therefore, the problems caused there are still consistent with my statement above. All JavaScript code runs until there is a break. Breaks are caused by alerts, ends of functions (that do not immediately return to another function) and timeouts (but are actually an end of function w/o an immediate return to another). I'll keep looking for the article, it was about 3 years ago that I read it. Here's an example of how various loops will execute. Notice that only ends of functions and alerts allow the browser to begin its work:
==========================
<html>
<head>
<title>Page</title>
<script language="JavaScript">
function runTest1()
{
for(var i = 0; i <= 10; i++)
{
document.getElementById("t
}
}
function runTest2()
{
for(var i = 0; i <= 10; i++)
{
setTimeout("document.getEl
}
}
function runTest3()
{
var count = parseInt((arguments[0] || 0));
if(count > 10) return;
document.getElementById("t
setTimeout("runTest3(" + (count + 1) + ");", 0); // Timeout will not run in IE until after the current function completes
}
function runTest4()
{
for(var i = 0; i <= 10; i++)
{
document.getElementById("t
alert("Causing a break in JS execution to allow browser to execute commands");
}
}
</script>
</head>
<body>
<input type="button" value="Run Test 1" onclick="javascript:runTes
<input type="button" value="Run Test 2" onclick="javascript:runTes
<input type="button" value="Run Test 3" onclick="javascript:runTes
<input type="button" value="Run Test 4" onclick="javascript:runTes
<br><br>
Test1: <div id="test1"></div>
Test2: <div id="test2"></div>
Test3: <div id="test3"></div>
Test4: <div id="test4"></div>
</body>
</html>
I'm not sure what you are trying to demonstrate above as the window remains open with each test.
Look, the only thing I'm advocating is that as a best practice it is better to do all the work you want a window to do before you close it -- otherwise you are taking a chance that a slower or resource-constrained client might not finish the work to be done after the close() statement is executed. As to a submit being on its own thread -- only if it is submitted to a different window.
The only thing I was demonstrating is that the browser will not do "it's thing" until the JavaScript function is complete and that includes window.close().
REGARDLESS of how fast/slow their browser is, the close() will NOT execute until JavaScript has completed it's execution. That's all. The reason I put the focus() after the close() was so that the focus was intuitively after the closing. In actuality, the focus() will happen BEFORE the close() because it is acting on a different window, in a different thread, as can be seen in the following popup example. Notice that the opener window takes focus before the popup closes. The 1mil loop is to simulate a "slow" browser. Watch as the close() is delayed until the loop is complete, that is because the close() will not execute until after the looping is done. I've added an onbeforeunload handler to alert the value that was incremented so as to better prove the point.
If there is <i>any</i> point to this at all, it is to prove that I put focus() after close() in order to delay the focus() until the last possible moment before the browser is closed and reduces the delay between the focus() and the close() so that there is less time for a user to click elsewhere and lose focus of the opener.
=======================
<html>
<head>
<title>Page</title>
<script language="JavaScript">
var i = 0;
function runTest()
{
self.close();
window.opener.focus();
for(i; i < 1000000; i++)
continue;
}
window.onbeforeunload= function(){
alert(i + " was reached!");
}
</script>
</head>
<body>
<input type="button" value="Close" onclick="javascript:runTes
</body>
</html>
>> REGARDLESS of how fast/slow their browser is, the close() will NOT execute until JavaScript has completed it's execution. That's all.
This is simply not correct for all implementations. I'm sure you know that javascript is not multi-threaded, it is executed sequentially. Despite this, a particular client (browser) might make use of the multi-threading provided by the OS to perform certain tasks, such as closing the window. So when (some) browsers encounter a window.close() they might make an asynchronous call to close the window while allowing the single-threaded javascript engine within the window to continue executing the next line of code (parent.focus() in this case). But whether or not it finishes executing this code is a matter of timing -- as my previous code has already demonstrated. Perhaps there are implementations that work as you have described -- but I am not aware of any (and I admit I don't know many of them).
<HTML>
<HEAD>
<SCRIPT language="javascript">
function test()
{
self.close();
document.myform.submit();
}
</SCRIPT>
<BODY>
<FORM name="myform" action="posthandler.asp" > <!-- adding a target here might work if your timing is right -->
<INPUT type="button" value="test" onclick="test();" />
</FORM>
</BODY>
</HTML>
GameQuestions -- please accept my apologies for all this. Post your code and we will try to help.
Business Accounts
Answer for Membership
by: dbrittPosted on 2005-11-22 at 05:56:14ID: 15341636
self.close();
window.opener.focus();