Did so - WICKET-5104 <https://issues.apache.org/jira/browse/WICKET-5104>
I still don't understand what the problem is. Despite the error things seem to be working. Is it safe to ignore it, or should I find a workaround until it is fixed? On Sat, Mar 16, 2013 at 8:53 AM, Sven Meier <s...@meiers.net> wrote: > Seems like this is caused by WICKET-4959. > > Please file a Jira issue. > > Sven > > > On 03/15/2013 09:56 PM, Marios Skounakis wrote: > >> Hi all, >> >> I am using a modal window as a substitute for messageboxes. E.g. I have a >> few forms with an ajax submit button, and I am using the modal window to >> first display a confirmation message, and if the user accepts it, to >> display a success / failure message. >> >> I am getting frequent errors in the Wicket Ajax Debug console. One is: >> * >> ERROR: * >> >> Wicket.Ajax.Call.**processEvaluation: Exception evaluating javascript: >> TypeError: Wicket.TimerHandles is undefined, text: >> (function(){clearTimeout(**Wicket.TimerHandles['**spinner21e']); delete >> Wicket.TimerHandles['**spinner21e'];})(); >> >> The spinner control mentioned above is an image component with an >> AbstractAjaxTimerBehavior. In all cases of error, it has >> setVisibilityAllowed(false) (it's hidden). >> >> Usually the errors can be ignored and the page still functions normally. >> >> I've never really dug into the way ajax responses are handled so I'm not >> sure where to start in order to track this error down. >> >> Any ideas? >> Thanks in advance, >> Marios >> >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org> > For additional commands, e-mail: users-h...@wicket.apache.org > >