The random parameter is there to prevent caching of the Ajax response. AFAIK clicking on a tab will reload its content each time. I.e. Wicket doesn't "think that the tab is already loaded".
On Thu, Apr 28, 2011 at 12:41 AM, Matthew Goodson <[email protected]> wrote: > Yeah I'm not feeling too hopeful > I have a tabbed panel which loads the tabs via ajax. When the page is loaded > from the browsers cache i.e. the user hits the back button, the ajax request > to load the tab is sent but wicket thinks that tab is already loaded > (getSelectedTab()) so ignores the request. > > Here's the request that's sent. Wicket adds the random parameter. I'm not > sure if I removed the random param (somehow) if that would breaks things. > > http://localhost?wicket:interface=:27::IActivePageBehaviorListener:21:2&wicket:ignoreIfNotActive=true&tab=privacysettings&random=0.8811610792763531 > > Any ideas? > > > On Wed, Apr 27, 2011 at 7:22 PM, Martin Grigorov <[email protected]>wrote: > >> Hi, >> >> I'm not sure whether this is possible at all. >> Why do you need to do this ? >> >> On Wed, Apr 27, 2011 at 8:12 AM, Matthew Goodson >> <[email protected]> wrote: >> > Hi guys, >> > I'm trying to find out if an ajax request has come from page that was >> loaded >> > from the browsers cache. Does anyone have any ideas of how I could >> achieve >> > this? >> > Thanks >> > >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
