Thanks for the replies guys. Nope, not a JSON problem... The client IDs are correct, as the debugger tells me, but for some reason the event handler for the form submit button isn't getting called after a zone refresh. I guess this question is invalid, something else is going on.
On Oct 25, 2011, at 6:29 AM, Barry Books wrote: > Are you using JSONLiteral in your mixin? > > If your mixin does some javascript and stops working with no errors > after a zone refresh I would suspect the JSON returned on the zone > update is invalid. When this happens the JSON parser traps the error > so you don't see any problems but nothing works after that. > > The changing client IDs can also be a problem. I wrote a selector > binding for the tapestry5-jquery library that helps with that issue. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
