D
Dag Sunde
Is there a way to detect if the reason an onUnload()
handler was called originated from the user explicitly
refreshed the page(s)?
Ie. pressed "Ctrl-R", "F5" or klicked the refresh button
in the toolbar or the context menu?
I'm aware that I can not stop a refresh, but the reason
I want to know is that I have a hidden frame in an intranet
application. This hidden frame is present at all times after
the user have sucessfully logged in (to our db).
So the only time this frame is closed is when the user
navigates away from the intranet app. At which point I want
to log him/her out.
I do thid With an AJAX call in the unload-event of the hidden
frame.
*BUT*... This leads to logging out if the user presses "F5",
or in other ways refresh the window, since a refresh reloads
both frames.
So I thought that if I could detect that this was a refresh in
progress, I can avoid logging him/her out.
PS!
I only need this to work in an IE-only scenario.
TIA...
handler was called originated from the user explicitly
refreshed the page(s)?
Ie. pressed "Ctrl-R", "F5" or klicked the refresh button
in the toolbar or the context menu?
I'm aware that I can not stop a refresh, but the reason
I want to know is that I have a hidden frame in an intranet
application. This hidden frame is present at all times after
the user have sucessfully logged in (to our db).
So the only time this frame is closed is when the user
navigates away from the intranet app. At which point I want
to log him/her out.
I do thid With an AJAX call in the unload-event of the hidden
frame.
*BUT*... This leads to logging out if the user presses "F5",
or in other ways refresh the window, since a refresh reloads
both frames.
So I thought that if I could detect that this was a refresh in
progress, I can avoid logging him/her out.
PS!
I only need this to work in an IE-only scenario.
TIA...