That worked perfectly, and cleaned up the code quite nicely. Thanks for the tip.
Regards, Travis Romney On Tue, Nov 2, 2010 at 7:22 AM, LLTYK <ll...@mailinator.com> wrote: > > The main reason I see for events suddenly stopping is the element you > observed being inside the zone, and being trashed on zone reload. > > I feel like you should actually be using a mixin on the textfield, since > that's probably where you want the keyup events. A mixin will automatically > reinitialize it's javascript again on zone reload, and also get a handle on > the tapestry generated id instead of a hardcoded one as well. > -- > View this message in context: > http://tapestry-users.832.n2.nabble.com/Mixing-zone-updates-and-custom-events-tp5695382p5697155.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
