Er, don't? I mean, is that really a "bug"? (as far as GWT is concerned, it's not, it's by design)
handleCurrentHistory "updates" your *app* with the place corresponding to the *current* history token (which might not exist, it's then the "default place" you given when initializing the PlaceHistoryHandler), not the other way around. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/uOuo7YJOEX8J. 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.
