Details
-
Question
-
Status: Closed
-
Minor
-
Resolution: Done
-
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 zone2 javascript Tapestry.ZONE_UPDATED_EVENT.
Is this a bug or meant behaviour?
The problem I had was that I had javascript code in zone1 Tapestry.ZONE_UPDATED_EVENT that should not be executed everytime an inner zone is updated.