Done, https://issues.apache.org/jira/browse/TAP5-1866
Please also see: https://issues.apache.org/jira/browse/TAP5-1867 which is a blocker for 1866. Cheers, Dragan Sahpaski On Thu, Mar 8, 2012 at 12:28 PM, Taha Hafeez Siddiqi < tawus.tapes...@gmail.com> wrote: > Hi Dragan > > Great! Please open a Jira and attach the patch. > > Sent from my iPhone > > On Mar 8, 2012, at 4:05 PM, Dragan Sahpaski <dragan.sahpa...@gmail.com> > wrote: > > > Hi, > > We have the following use case: > > A zone with a ZoneRefresh (located in another zone) is updated several > > times and then the outer zone is updated with another block. > > After the update, exceptions are constantly thrown by the javascript > > PeriodicUpdater on this line > > "zoneRefresh.fire(Tapestry.ZONE_REFRESH_EVENT)" because the div element > > that's linked to the zone with Tapestry.Initializer.updateZoneOnEvent is > > not destroyed and the corresponding timer is also not destroyed. > > > > I think the ZoneRefresh mixin should cleanup after itself in scenarios > like > > this. > > > > If someone this this idea is solid and back it up, I'm willing to work on > > implementing a patch. > > Clearly the improvement code would be internal (mainly javascript and > tests > > to back it up), and won't involve public API changes. > > > > Cheers, > > Dragan Sahpaski > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
