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 !
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,
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,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
