I've wondered the same thing. I believe it was part of the clearing out of client-side JavaScript effects that relied on Scriptaculous. http://tapestry.apache.org/ajax-and-zones.html says: "For 5.4, there are client-side events that are triggered before and after changes to the Zone; listeners on those events can trigger whatever animations they like". However, that doesn't really answer the question.
On Wed, Aug 6, 2014 at 6:32 AM, Muhammad Gelbana <m.gelb...@gmail.com> wrote: > Why is Zone's *visible* parameter deprecated ? > > Is there another Tapestry way to initially hide a zone ? > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
