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

Mike Hanafey commented on RF-7395:
----------------------------------

Seems this is a simple fix and could be also be applied to the up comming 3.3.2 
release?

A very useful tableStyle is "width=100%", because this makes the position of 
the next and previous pages control fixed (rather than jumping around as the 
number of pages with 1, 2, 3... numbers changes).

Also the documentation should make it clearer that the "for" attribute is 
optional, and the scroller can be placed in the header of a table. This is a 
much better place for tables where the vertical height of rows is not fixed, 
because in this case the footer is jumping around (maybe off the page even) as 
the user scrolls through pages.

> dataScroller: tableStyle doesn't work
> -------------------------------------
>
>                 Key: RF-7395
>                 URL: https://jira.jboss.org/jira/browse/RF-7395
>             Project: RichFaces
>          Issue Type: Bug
>          Components: component-tables
>    Affects Versions: 3.3.2.CR1
>         Environment: all provided browsers
> rfVersion - v.3.3.2-SNAPSHOT
>            Reporter: Vadim Mikovoz
>            Assignee: Anton Belevich
>            Priority: Minor
>             Fix For: 4.0.0.ALPHA2
>
>
> Define tableStyle attribute for dataScroller, e.g.:
> tableStyle="background-color: red; font-style: oblique;"
> 1. Open test page
> 2. Look at the dataScroller
> ------------------------------------
> tableStyle didn't apply

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to