You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Oliver Pelz (JIRA)" <ji...@apache.org> on 2010/11/18 16:11:15 UTC
[jira] Created: (TAP5-1351) Multiple Grids with pagination on one
page interfer with each oter
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
Priority: Critical
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1351) Multiple Grids with pagination on one
page interfer with each oter
Posted by "Yves Lalanne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981145#action_12981145 ]
Yves Lalanne commented on TAP5-1351:
------------------------------------
Actually, this bug is linked with https://issues.apache.org/jira/browse/TAP5-255 : Grid component wrap its template in a Zone component, as shown in Grid's beginRender(MarkupWriter writer) method.
So following tapestry's documentation about ajax support and zone limitations http://tapestry.apache.org/ajax-javascript.html#Ajax%26JavaScript-ZoneLimitations we could see "Tapestry will uniqueify client id [of zone components inside a loop]". So we've only one accessible grid.
The fix is thus given by Giulio Micali.
> 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
> Priority: Critical
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (TAP5-1351) Multiple Grids with pagination on one
page interfer with each oter
Posted by "Howard M. Lewis Ship (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1351:
---------------------------------------
Priority: Major (was: Critical)
Apparently there's a workaround, so it's annoying but not critical.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1351) Multiple Grids with pagination on one
page interfer with each oter
Posted by "Howard M. Lewis Ship (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1351:
---------------------------------------
Priority: Major (was: Critical)
Apparently there's a workaround, so it's annoying but not critical.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TAP5-1351) Multiple Grids with pagination on one
page interfer with each oter
Posted by "Yves Lalanne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981145#action_12981145 ]
Yves Lalanne commented on TAP5-1351:
------------------------------------
Actually, this bug is linked with https://issues.apache.org/jira/browse/TAP5-255 : Grid component wrap its template in a Zone component, as shown in Grid's beginRender(MarkupWriter writer) method.
So following tapestry's documentation about ajax support and zone limitations http://tapestry.apache.org/ajax-javascript.html#Ajax%26JavaScript-ZoneLimitations we could see "Tapestry will uniqueify client id [of zone components inside a loop]". So we've only one accessible grid.
The fix is thus given by Giulio Micali.
> 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
> Priority: Critical
>
> 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.
-
You can reply to this email to add a comment to the issue online.