>>No, it didn't work. Basically, I just sent the function back to the browser from the backend, which is suppose to give the same thing and the focus goes back to the initial window. I also tried to use window.history.back() syntax instead of the window.history.go(-1) syntax. It gave the same result.
>>
>>The focus goes to the initial window as soon as the called window has finished loading all of its frames. Might it be related?
>
>Sorry it didn't work for you.
>If you have a code snippet from your actual page(s) and the sequence in which the server returns it/them, that would be helpful; I am now curious as to why it doesn't work in your scenario.

The code snippet is the login form from the main page. The code returned is the following:

< SCRIPT>
window.open("http://www.levelextreme.com/wconnect/wc.dll?UniversalThread~?
 2,19,50,50","_blank","scrollbars=yes,width=1000,height=750,resizable=yes,
 toolbar=yes,menubar=yes,status=yes,location=yes")
window.history.back()
< /SCRIPT>

I also tried as suggested to have the following:

< SCRIPT>
var newWin=window.open("http://www.levelextreme.com/wconnect/wc.dll?UniversalThread~?
 2,19,50,50","_blank","scrollbars=yes,width=1000,height=750,resizable=yes,
 toolbar=yes,menubar=yes,status=yes,location=yes")
window.history.back()
newWin.focus()
< /SCRIPT>

You'll see that this transaction fires a framing environment. I suspect that to be the problem.