You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/12 09:11:06 UTC

[jira] [Closed] (TAP5-1552) Ajax and Zones documentation should explain zones in loops using id attribute

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

Jochen Kemnade closed TAP5-1552.
--------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

> Ajax and Zones documentation should explain zones in loops using id attribute
> -----------------------------------------------------------------------------
>
>                 Key: TAP5-1552
>                 URL: https://issues.apache.org/jira/browse/TAP5-1552
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Josh Canfield
>
> http://tapestry.apache.org/ajax-and-zones.html
> In Zone Limitations says:
> Unlike many other situations, Tapestry relies on you to specify useful and unique ids to Zone components, then reference those ids inside EventLink (or ActionLink, or Form) components. Using Zone components inside any kind of loop may cause additional problems, as Tapestry will uniqueify the client id you specify (appending an index number).
> Using a generated "id" attribute allows you to control the id of the zone in the page.



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