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

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1552:
---------------------------------


This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

> 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.2#6252)