You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Nathan Quirynen (Created) (JIRA)" <ji...@apache.org> on 2012/03/15 09:17:38 UTC
[jira] [Created] (TAP5-1876) Zone update for nested Zone triggers
outer Zone javascript update event
Zone update for nested Zone triggers outer Zone javascript update event
-----------------------------------------------------------------------
Key: TAP5-1876
URL: https://issues.apache.org/jira/browse/TAP5-1876
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.3
Reporter: Nathan Quirynen
Priority: Minor
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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1876) Zone update for nested Zone triggers
outer Zone javascript update event
Posted by "Nathan Quirynen (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Quirynen closed TAP5-1876.
---------------------------------
Resolution: Invalid
> Zone update for nested Zone triggers outer Zone javascript update event
> -----------------------------------------------------------------------
>
> Key: TAP5-1876
> URL: https://issues.apache.org/jira/browse/TAP5-1876
> Project: Tapestry 5
> Issue Type: Bug
> 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 zone2s Tapestry.ZONE_UPDATED_EVENT.
> Is this a bug or meant behaviour?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1876) Zone update for nested Zone triggers
outer Zone javascript update event
Posted by "Nathan Quirynen (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Quirynen closed TAP5-1876.
---------------------------------
Resolution: Invalid
> Zone update for nested Zone triggers outer Zone javascript update event
> -----------------------------------------------------------------------
>
> Key: TAP5-1876
> URL: https://issues.apache.org/jira/browse/TAP5-1876
> Project: Tapestry 5
> Issue Type: Bug
> 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 zone2s Tapestry.ZONE_UPDATED_EVENT.
> Is this a bug or meant behaviour?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira