We lots of problems with onUnload() and found that it could not be effectively used to log a user out. I believe that in Netscape, the windows was closing before the onUnload() event actually finished executing. After a while we gave up and went back to to just timing out sessions.
Justin > -----Original Message----- > From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 22, 2002 9:14 AM > To: CF-Talk > Subject: Re: OT: onUnload() Issue within a CF Application. > > > Oliver Cookson wrote: > > >> What I'm planning to do is popUp a window onUnload() which > log's the > >> user out, easy you say, well how do I STOP the window > popping up when > >> they user the back\forward buttons or press refresh? > > > onClose() > > > Jochem > > Except that this doesn't satisfy the condition of moving the > browser out of > the application by typing a url into the address field, thus > leaving the > user stranded and unable to log back in if they for instance, type > www.google.com into the address field, browse to another > page, then close > the browser. > > I know of a way to prevent any users not using Internet Explorer from > logging in to an application ( including preventing users of current > versions of Opera ). This may or many not be a solution for > you, however, if > you can control the browser environment, then you can do some > things that > you might not otherwise consider for compatibility reasons. I > have an app > currently using a hidden iframe to submit the login command on the > onbeforeunload() event which has proven to be more effective > than onunload() > or a popup window ( which are often killed before they open > ). What I found > using onunload() was that I could only get the url to fire in > a killable > popup -- it wouldn't load in the iframe. But onbeforeunload() > gave me the > functionality I needed. > > As to the back, forward and refresh I don't really have a > solution -- the > application I just mentioned has a console in the topmost window which > mostly doesn't move or reload (it reloads in a couple special case > conditions, but it's able to do this without logging out), > with all of the > tools loading into iframes. The issue of back and forward is addressed > primarily by simply providing links in such a fashion that the user > hopefully never has a need for a back button. If a user hits f5 or the > reload button ( instead of right-clicking an iframe and > reloading the frame > ), they're logged out and they have to log in again. > > .. dunno how much help any of this is. :) > > s. isaac dealey 954-776-0046 > > new epoch http://www.turnkey.to > > lead architect, tapestry cms http://products.turnkey.to > > certified advanced coldfusion 5 developer > http://www.macromedia.com/v1/handlers/index.cfm?ID=21816 > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
