You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/25 02:19:49 UTC

[jira] [Commented] (TAP5-1351) Multiple Grids with pagination on one page interfer with each oter

    [ https://issues.apache.org/jira/browse/TAP5-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719080#comment-13719080 ] 

Howard M. Lewis Ship commented on TAP5-1351:
--------------------------------------------

And there's no longer a zone in 5.4, though there is something "zone like".  I'm not sure if the changes address this problem.
                
> Multiple Grids with pagination on one page interfer with each oter
> ------------------------------------------------------------------
>
>                 Key: TAP5-1351
>                 URL: https://issues.apache.org/jira/browse/TAP5-1351
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.15
>            Reporter: Oliver Pelz
>
> If more than one grid with pagination will be created on a single tapestry page, the pagination interfer each other.
> This seems because the multiple grids/paginations do not have unique ids.
> I issued this in tapestry-users a while back where I enclosed the grids into components but this also happens if you put more them unenclosed on the same page (http://tapestry-users.832.n2.nabble.com/Grids-embedded-in-custom-component-interfer-with-each-other-td5376183.html). If you then click on a pagination from one grid the others will be changed as well.
> You can find a testcode on the tapestry-users page here http://tapestry-users.832.n2.nabble.com/Grids-embedded-in-custom-component-interfer-with-each-other-td5376183.html which capsulates the grids into components but this interefers as well as putting multiple grids without components on the same page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira