[richfaces-issues] [JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929593#comment-12929593 ] 

Brian Leathem commented on RF-13427:
------------------------------------

Given that the server does not know the cell-height content at the time the response is rendered, there is no way to tailor the number of rows rendered to the content height.  I suggest you rethink your layout constraint for a fixed hight table.

Can you propose a solution (conceptually) for the problem you are describing?
                
> ED, Datatable: table needs to define the number of rows itself when using dataScroller
> --------------------------------------------------------------------------------------
>
>                 Key: RF-13427
>                 URL: https://issues.jboss.org/browse/RF-13427
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>         Attachments: data-3.png, datatable-1.png
>
>
> I need using pagination for extendedDataTable control.
> My row's height depends on the data it contains.
> I need the table to be constant height, so I specify the height in css.
> I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller.
> So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears.
> Both situations are not user friendly.
> Actually on each page I need the maximum rows number to fit the height.

--
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