disable security prompt when closing window 1

[sweetleaf]

hi,

does anyone know how to disable the prompt you get when trying to close a window not opened from javascript.
ie. with server script i submit abc.asp to def.asp but def.asp does not redirect, so i'd like to close it.

thx

 

[jaredn]

This is a built in security feature. I do not thing you can disable it, unless you are a trusted app of some sort (HTA??) jared@aauser.com

 

[jaredn]

more on HTA's here:

http://msdn.microsoft.com/workshop/author/hta/overview/htaoverview.asp

though I'm not positive that iwll solve the problem... jared@aauser.com

 

[sweetleaf]

thanks jared,
unfortunately i am in a position where i cannot re-write the app as an hta(as its a group project).so far i think that the only way a window can be closed without the prompt is when it's opened from client script - in my case i'm submitting form data to it:

window.frm1.action = "processNewDll.asp"
window.frm1.submit

regards

 

[jaredn]

hmm, im kinda confused now.

Take me through the steps... you never open the window? The user justs open IE, submits the form and you want the browser to immediately close (after submission to the correct page)? jared@aauser.com

 

[froggerIII]

sweetleaf, I would like to be able to do the same thing too, but as far as I know, you only have rights to close windows that you have dynamically created.

I was thinking that maybe for ie, you could somehow write an activex object that automatically does a keypress or mouseclick to close that popup window? ray
rheindl@bju.edu

 

[sweetleaf]

hey jared,

the user completes an input screen (modal dialogue)- its contents are submitted to another page. the second page opens and does not need to redirect back(modal) ,and so i'd like to close it.
everything works but disabling the prompt. for now an instruction to the user is written to the screen("pls click CLOSE next&quot, and when the window is closed they are brought back to the modal dialogue box with the data entered.

 

[sweetleaf]

hi froggerIII, a simulated keystroke or click might produce similar results , however - only at a different window..
there must be a way to intercept the "message" coming from the dll responsible for this prompt.