Hi, has no-one observed this yet? Shall I file an issue?
Bye Stefan Stefan Renz wrote: > Hi, > > I've observed the following behavior with WiQuery's Tabs-component: > after reloading a page with a tabs component on it (or by navigating the > browser history), one can't switch the active tab anymore -- the > component always jumps back. The browser makes a new request. > Apparently, Wicket loads a specific page version from the page store, > which is stuck on the tab. Removing the version number from the URL > works as expected. > > Did anyone also observe this behavior, or has anyone a suggestion to > workaround or fix that? > > The least thing I could do is to come up with a quickstart for this, > which is attached. > > We're talking about Wicket 6.6.0 and WiQuery 6.6.0 here, I've also tried > with 6.5.0. > > Thanks, bye > Stefan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- im Auftrag der eFonds Solutions AG, +49-89-579494-3417 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
