Hi, On Thu, Jul 7, 2016 at 11:28 PM, Martin Grigorov <[email protected]> wrote:
> Hi, > > It seems you use Wicket for several years now and you have no idea how to > use it! > Yes perhaps Martin, I do try but there's a lot too it. > > I have done this for a client of mine 4 years ago. > And I have explained how to do it few times in the mailing lists. > You could use HTML5 History API to manipulate the browser url on each Ajax > call. If you need to support old browsers (why?! almost no one does these > days) then you should use some JS library that falls back to using the > location fragment/hash. > The support of "back/forward" buttons is just registering an > AjaxEventBehavior that listens for "popState"/"hashchange" event. > > I did some extensive searching and only found a couple of threads about this: http://apache-wicket.1842946.n4.nabble.com/Wicket7-History-API-support-for-navigable-AJAX-pages-components-td4660502.html The main issue seems that the page map is not updated (just overriden) for ajax requests from my reading before. I came to the conclusion trying to get wicket to support the back button would be difficult and somewhat hacky. It seems we'd end up with unknown behaviour and issues possibly occurring and therefore too much of a risk. Hence this thread. > > I will try to find time to write a blog article with a demo app at > wicketinaction.com soon. > > That would be great. > >
