My favorite reply, a mixin on a component in a zone will get it's javascript run again on zone update. So you make a mixin that handles both disabling and enabling, it will run on page render, and run again whenever you update the zone.
Oh, and use renderSupport.addScript, like in here: http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/creatingmixins1 -- View this message in context: http://tapestry-users.832.n2.nabble.com/5-1-0-5-Firing-javascript-from-page-class-from-mixin-handler-method-tp5556060p5558626.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
