Check wicketstuff's jquery project for HistoryAjaxBehavior. May be it helps.
drf wrote: > > I have encountered the following serious issue: > > My application consists of one WebPage which has an AjaxTabbedPanel. Each > tab has an associated panel which includes several menu items (links) > which can be selected. This works well. > However, if the user selects the back-button (once back, then once > forward) they can come back to the page with a different tab displayed > than the one selected before the back-button was used. If a menu link is > then clicked on, an exception is thrown. This appears to be because the > Wicket on the server is now out of synch with the html displayed. Wicket > thinks a different panel is selected than the one the user sees now. > > This appears to be a fundamental Wicket problem/issue - apart from > disabling the back button, what are the available approaches? > -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/back-button-causes-Wicket-state-and-page-displayed-to-be-out-of-synch-tp3006971p3008140.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
