Yes, the changing of the client IDs to semi-random ones was what I suspected before (hence my previous thread) but after some debugging, it turns out that the mixin gets initialized after the zone update with the new client IDs correctly and something else is going on. It seems like the AJAX event from the mixin to the server stops working, i.e. onsubmit() winds up doing a no-op even though JS calls the server with the form.
On Oct 25, 2011, at 1:26 PM, cqasker wrote: > When you get the ajax response back, did any of ids change? The stuff in the > zone changes but the javascript code from the mixin doesn't . I am not an > expert but thats the only thing I can think of. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
