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:
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
Hi !
Thanks for your reply and link !
I still have one question : why does it happen on IE8 64 bits and not on IE8
32bits ?
I don't get why IE8 64bits seems to have a smaller stack size.
--
View this message in context:
Hi,
On Fri, Apr 26, 2013 at 9:29 AM, M4xime maxime.nou...@capgemini.com wrote:
Hi !
Thanks for your reply and link !
I still have one question : why does it happen on IE8 64 bits and not on
IE8
32bits ?
I don't get why IE8 64bits seems to have a smaller stack size.
No idea. IE is not
Hi,
thanks for your reply.
The problem is that there is a wicket upgrade scheduled in...2014.
So, i have to find something to show to my client so that he understands why
ie64 must not be used before the upgrade.
I searched wicket's JIRA but i did not find any issue about my problem.
Can you
Hi,
One of the bigger changes Wicket 5 and 6 is in wicket-ajax.js.
Part of the changes include improvements in FunctionsExecuter which causes
you problems.
Additionally Wicket optimizes the amount of steps the FunctionsExecuter
does by minimizing the number of evaluate elements in the Ajax
Hi,I've got a problem with some ajax request on IE8 64 bits.After closing a
pop-up, which imply a refresh of the page, an IE pop-up saying
StackOverflow appears.It does not happen on IE8 32 bits.The IE debugger
points to notify(); at the line 931 of wicket-ajax.jstry { eval(text);}
catch
Hi,
This part of the code is improved in Wicket 6.x.
You are recommended to upgrade to Wicket 6.7.0.
On Wed, Apr 24, 2013 at 1:02 PM, M4xime maxime.nou...@capgemini.com wrote:
Hi,I've got a problem with some ajax request on IE8 64 bits.After closing a
pop-up, which imply a refresh of the
