tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1877) Zone update for nested Zone triggers outer Zone javascript update event
Date Tue, 25 Aug 2015 11:58:46 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-1877.
--------------------------------
    Resolution: Done

If nested Zones behave that way, it's a bug. Please reopen the issue if you're still seeing
this behavior in recent versions (5.3.8 or 5.4-beta-35).

> Zone update for nested Zone triggers outer Zone javascript update event
> -----------------------------------------------------------------------
>
>                 Key: TAP5-1877
>                 URL: https://issues.apache.org/jira/browse/TAP5-1877
>             Project: Tapestry 5
>          Issue Type: Question
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Nathan Quirynen
>            Priority: Minor
>              Labels: event, javascript, zonerefresh
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message