Hi, The simplest solution is to decrease the number of steps which FunctionsExecutor can do before using setTimeout() to start a new stack.
On Tue, Apr 30, 2013 at 2:05 PM, M4xime <maxime.nou...@capgemini.com> wrote: > Hi, > > In the end, I have to find a workaround to fix this bug. > > Do you think that overriding a part of wicket's js code can work ? > > Is there a part of the code of a more recent version that can be used to > replace the incriminated code? > > Thanks ! > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-9-StackOverflow-wicket-ajax-js-with-IE8-64bits-tp4658229p4658412.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov Wicket Training & Consulting http://jWeekend.com <http://jweekend.com/>
