javascript - Handling Application abandonment -


I have an application which spreads many pages of engagement for the applicant and I do not want the user to be long ago

Without kidnapping back and forward button (I think most of the forum will agree that this is a bad practice) I have onbeforeunload Which handles some of the typical use cases where the system could consider the fluctuation of the document Land, the user is equivalent to leaving the application, that page refresh (F 5, Ctrl / Meta + R).

However, do I have to woo how to allow movement in the context of the application, such as page 1> submit> PG2> ops, back button> page 1. or where the URL is physically May be but the application is still "in the area".

What happens by using the back button to return to PG 1 (or forward to go back to PG2) onbeforeunload fire ( which is expected ), it seems that the applicant should leave the application Maybe .

What I see and woo me is the power to inspect the destination document / domain. I would like, in this way the user experience is not ugly, press the "Please do not leave" dialog only when the next page is not going to be in my application domain.

Suggestions?

Instead of using different pages, will you be able to use multiple devices on the same page? If you are using ASP.NET, then you can also use the user control for better code isolation on the Codebahind side. I still keep the divas as the top-most tags in the user control.

Each devel is in line with what is currently explained in a web page. Depending on the user pressing the back or forward button, you can enable visibility on the appropriate div.

HTH ...


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -