Hi All,
I donno whether I could understand the problem here completely.
but I was also facing same kinda problem. and I was not using the History
managment.
but ever since i started using it, the problem solved.
below is the code which keeps user on same page even if the user refresh the
page.
in my AppController.java :-
if ("".equals(History.getToken())) {
History.newItem("list");
} else {
*History.fireCurrentHistoryState();*
}
for details :-
http://code.google.com/webtoolkit/articles/mvp-architecture.html#history
--
Sarjith
On Fri, Feb 18, 2011 at 2:27 AM, Sky <[email protected]> wrote:
> No, you always get the Confirmation dialog.
>
> Read my post carefully. I describe the correct way of doing this. You
> should NOT be preventing the user from leaving the page! They would not be
> able to go to your site and then decide to go to www.google.com, for
> example, in the same tab and this will piss ppl off and they won't want to
> go to your site.
>
> Your gwt code simply needs to check to see if they have already logged in
> and then decide to NOT display the login page and instead build the site
> according to the History token.
>
> You absolutely have to do it this way. There is no work around.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
