You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Josh Canfield (JIRA)" <ji...@apache.org> on 2011/06/22 00:17:49 UTC
[jira] [Created] (TAP5-1552) Ajax and Zones documentation should
explain zones in loops using id attribute
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
Priority: Minor
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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1552) Ajax and Zones documentation should
explain zones in loops using id attribute
Posted by "Josh Canfield (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Canfield updated TAP5-1552:
--------------------------------
Priority: Major (was: Minor)
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1552) Ajax and Zones documentation should
explain zones in loops using id attribute
Posted by "Josh Canfield (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Canfield updated TAP5-1552:
--------------------------------
Priority: Major (was: Minor)
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira