I've had the same requirement a couple of times. The way I've settled on
doing it, whether it's the best or not I don't know, is this...
I used client-side scripting to prompt the user whether they want to save
or not (just some simple dirty data checking, i.e., any time they press a
key I set a
You won't be guaranteed to catch any event like browser close or the user
clicking alternate navigation, bookmarks or even typing in a new url.
If it were are definite requirement, you could simply attempt to catch that
even, then prompt the user with something like "Warning - you have unsaved
cha
2 matches
Mail list logo
