[jira] [Updated] (TAP5-1066) Client-Id and Links in Grid not correct when putting a Grid inside a Loop

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

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

Jochen Kemnade updated TAP5-1066:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Client-Id and Links in Grid not correct when putting a Grid inside a Loop
> -------------------------------------------------------------------------
>
>                 Key: TAP5-1066
>                 URL: https://issues.apache.org/jira/browse/TAP5-1066
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Matthias Jell
>              Labels: bulk-close-candidate
>
> I write a page with a grid component inside a loop. For every iteration result in the loop I generate a new display bean model as grid model.
> The page will be rendered and it looks fine, but only the first grid getting a client-id and all sorting links of all grids inside the loop use this clientId. 
> In my opinion every grid should have a single clientId.
> ....
> <t:loop source="abc" result="xyz">
>    <t:grid />
> </t:loop>



--
This message was sent by Atlassian JIRA
(v6.2#6252)