I'm using Wicket-1.x from SVN and in Safari 2.0.4 when I try to replace a number of components and partially update the page I get an error:

ERROR: Error while parsing response: Maximum call stack size exceeded.

This same code works in 1.2.2.

I traced the problem to the Wicket.FunctionsExecuter.processNext() function (line 120 of wicket-ajax.js):

if (this.depth > 50 || Wicket.Browser.isKHTML()) {
  // to prevent khtml bug that crashes entire browser
  // or to prevent stack overflow
  this.depth = 0;
  window.setTimeout(run, 1);
} else {
  this.depth ++;
  run();
}

I put a log message above the if statement that printed the value of this.depth and Safari goes to 11 and then crashes, so I changed the conditional to:

if (this.depth > 10 || Wicket.Browser.isKHTML()) {

and everything works correctly.

Could something I'm doing be causing this problem?  Or is this a bug in Wicket-1.x?

--
Caleb Land
([EMAIL PROTECTED])
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to