Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Invalid
-
5.3
-
None
Description
When having nested Zone components like:
<t:Zone t:id="zone1" id="zone1">
<t:Zone t:id="zone2" id="zone2">
<t:Form t:id="form" t:zone="zone2">
<t:Submit />
</t:Form>
</t:Zone>
</t:Zone>
Everytime the inner zone (zone2) gets updated/rerendered it fires up both zone1 and zone2s Tapestry.ZONE_UPDATED_EVENT.
Is this a bug or meant behaviour?