Page History

...

The Containing Zone (zone="^")

...

Since 5.2

...

If the Form or Link is enclosed by the Zone itself, and you're using the zone parameter instead of the async parameter, then the zone parameter may be set to the special value ^ (the carat). The zone is found – on the client side – by searching up form the form or link element for the first enclosing element that is a Zone. In this way, the client-side coordination can occur without having to know what the specific client-side id of the Zone is. Because of this, in some cases it is no longer necessary to specify the Zone's id parameter.

An Update div within a Zone div (Tapestry 5.3 and earlier)

...

Deprecated: This feature is removed starting with Tapestry 5.4

In many situations, a Zone is a kind of "wrapper" or "container" for dynamic content; one that provides a look and feel ... a bit of wrapping markup to create a border. In that situation, the Zone <div> may contain an update <div>.

...

Zone Effect Functions (Tapestry 5.3 and earlier)

...

Deprecated: This feature refers to client-side logic only present in Tapestry 5.3 or earlier. 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.

A Zone may be initially visible or invisible. When a Zone is updated, it is made visible if not currently so. This is accomplished via a function on the Tapestry.ElementEffect client-side object. By default, the show() function is used for this purpose. If you want Tapestry to call a different Tapestry.ElementEffect function when updates occur, specify its name with the zone's show parameter.

...