Reading up on it now... On 12/18/2009 5:15 PM, McIlwee, Craig wrote: > Maybe wicket thinks that the ajax behavior belongs to a page that isn't the > current/active page and therefore is ignoring it? > http://wicket.apache.org/docs/1.4/org/apache/wicket/ajax/AbstractDefaultAjaxBehavior.html#getCallbackScript(boolean) > Just a guess, and I am likely to be wrong, but I though I'd throw it out > there. > > Craig > _____ > > From: Kurt Heston [mailto:[email protected]] > To: [email protected] > Sent: Fri, 18 Dec 2009 19:45:36 -0500 > Subject: Re: Ajax not firing onSubmit after back-button press > > My Ajax calls are getting swallowed somewhere. Is there someplace I can > set a break-point to find out where it's dying? > > On 12/17/2009 11:28 AM, Kurt Heston wrote: > > I've read alot about ajax and the back button in the forums and on the > > web, but what I'm seeing looks to be a different problem in v1.4.3. I > > don't think it has anything to do with WICKET-271. > > > > I have some ajax in a panel that works perfectly after a page refresh > > but not after pressing the back button. I can see the call (POST) being > > made in FireBug and have confirmed it isn't being swallowed by Firefox > > caching with a JMeter proxy, but my onSubmit method isn't firing > > server-side. If I press the browser refresh button, onSubmit starts > > firing again. Not entirely sure, but I think this worked in v1.3.5. > > > > Suggestions? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
