All you get to work with is the state held in the history token, stuff in
cookies ... you can log the user back in to the application and use anything
you have on the server, but basically it's a refresh and if the user wanted
it in the state it was in before they hit F5, they wouldn't have hit F5.
You have to ask yourself what the user is trying to achieve by refreshing -
do they really want all the form fields filled with what was there before,
or are they trying to start again in the same condition but with a blank
form?
My strategy is to get the user back to the state they were in when they
first came to the page being shown if possible. (I use the word 'page' in a
GWT sense)
Ian
http://examples.roughian.com
2009/8/14 javier <jasand...@gmail.com>
> Hi there:
> there's plenty of documentation regarding the handling of the
> browser's back button with GWT's History tracking. I understand the
> concept of mapping a String token to a specific application state.
> Does GWT provide a mechanism to notify the application whenever the
> user clicks the browser's refresh button? (ie the equivalent to
> History.addValueChangeHandler() for the back button).
> Is there a recommended strategy for handling the browser's refresh
> button in the context of a GWT app? I'm curious to learn how are your
> applications currently dealing with this.
> Thanks in advance for any comments and suggestions.
> Javier.
