On Tue, Oct 25, 2011 at 8:12 PM, Lenny Primak <lpri...@hope.nyc.ny.us> wrote:
> 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. Out of curiosity... does this end up to something useful ? Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
