[richfaces-issues] [JBoss JIRA] (RF-12304) Two or more rich:extendedDataTable on page prevent selection on second extendedDataTable
Brian Leathem (JIRA)
jira-events at lists.jboss.org
Wed Oct 31 18:45:18 EDT 2012
[ https://issues.jboss.org/browse/RF-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730653#comment-12730653 ]
Brian Leathem commented on RF-12304:
------------------------------------
The javascript error is displayed in [line 310|https://github.com/richfaces/components/blob/develop/iteration/ui/src/main/resources/META-INF/resources/org.richfaces/extendedDataTable.js#L310], because the [scrollElement lookup|https://github.com/richfaces/components/blob/develop/iteration/ui/src/main/resources/META-INF/resources/org.richfaces/extendedDataTable.js#L172] fails. The renderer does not create the scrollElement if there aren't any [scrollable columns|https://github.com/richfaces/components/blob/develop/iteration/ui/src/main/java/org/richfaces/renderkit/ExtendedDataTableRenderer.java#L363].
The workaround then, is to make sure the number assigned to the _frozenColumns_ attribute of the dataTable is < the total number of columns.
To correct this problem, we can either change the condition which creates the scrollable element, or throw an exception when the number of frozen columns = the total number of columns.
> Two or more rich:extendedDataTable on page prevent selection on second extendedDataTable
> ----------------------------------------------------------------------------------------
>
> Key: RF-12304
> URL: https://issues.jboss.org/browse/RF-12304
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.2.Final
> Environment: jetty + tomcat 6 on win 7
> tomcat + Chrome + Linux
> Reporter: Britt Abel
> Labels: richfaces
> Fix For: 4.2.4, 4.3.0.M3
>
> Attachments: error.png
>
>
> If I place two or more extendedDataTables with selectionType="single" on one a page, it is only possible to make a selection on the first extendedDataTable. It is imposible to select a row on the second table. If I turn around the order of tables or delete the first one, it works fine for the other one. This means, the implementation itself shoul be correct,
> Do you have any ideas? Thanks for your help!!!
--
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
More information about the richfaces-issues
mailing list