window.open() not getting executed in IE (working in Firefox)

[hadoob024]

In a popup, I have a button. Here's how I defined the button:

<input type="button" name="generatePO" value="Z-PO" onclick="JavaScript:window.close();window.location='index.php?module=Patient_Procedure&action=genMFGPO'&pomode=create&kindofpo=Z';window.open(\'index.php?module=Patient_Procedure&action=genMFGPO&pomode=preview','poverifywin','width=1250,height=1000,status=0,resizable=1,scrollbars=1,toolbar=0,menubar=0,location=0')">

Basically, what it does is, close the popup, execute that window.location call which creates a PDF, then executes window.open() to open another popup to see if there are any more PDF's that can be created. This works fine in Firefox, but that window.open() never gets executed in IE 9.

Tried some google searches, but nothing came up.

I've rewritten this several times and can't get it to work in IE 9. Here's one of my rewrites:

<input type="button" name="generatePO" value="Z-PO" onclick="JavaScript:window.location='index.php?module=Patient_Procedure&action=genMFGPO'&pomode=create&kindofpo=Z';window.location.replace('index.php?module=Patient_Procedure&action=genMFGPO&pomode=preview');">

For some reason though, the window.open() doesn't get executed unless I click on the button twice. Can't think of how to fix this for IE. Thoughts???

[johanafm]

IE is correct in its behaviour. As soon as window.close is executed, window no longer exists, there will be no code to execute and there is no environment in which to executed. window.location followed by window.close is unreliable as well. Window.location is executed, but directly followed by window.close, which means that the request may or may not have time to be sent to the server before the connection is closed along with the window.

What you need to do is execute window.open to get a new window, directly followed by window.close in the existing window, or simply execute window.location in the current window and leave it open.

[johanafm]

IE is correct in its behaviour. As soon as window.close is executed, window no longer exists, there will be no code to execute and there would be no environment in which to execut it. window.location followed by window.close is unreliable as well. Window.location is executed, but directly followed by window.close, which means that the request may or may not have time to be sent to the server before the connection is closed along with the window.

What you need to do is execute window.open to get a new window, directly followed by window.close in the existing window, or simply execute window.location in the current window and leave it open.

[hadoob024]

Very cool! Thanks for the tip.

Quick question, that script that builds the PDF takes a couple of seconds to run. Is there something that I could do so that after the user clicks on the button, they don't click on it again until the whole process runs? I wonder if that's why the window.close was put in.

[Weedpacket]

You can set the button's disabled property to true; assuming JavaScript is running at all, that would disable it.

[hadoob024]

Perfect! That worked!