[
https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven W. updated RF-13126:
---------------------------
Description:
In prior 3.x release the ExtendedDataTable control supported TableState data
for sizing of columns - this worked relatively well *however* there is/was a
bug such that the columns headers above the table did *not* align properly with
the data rows of the table below; this could be partially accommodated by
specifying a size for the column (in the TableState data) that was wider than
the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored
and the TableState capability as a whole was lost - I saw this in another
report on the forum or Jira though not the same but other related issues may be
https://issues.jboss.org/browse/RF-4855 +
https://issues.jboss.org/browse/RF-13094 and
https://issues.jboss.org/browse/RF-13095 ; the report I remember reading,
however, is that this TableState functionality was lost during the refactoring
and was then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest
(overnight) snapshot and am confirming this TableState table header sizing
issue still remains, regardless of prior attempts to include TableState data
recognition and, if/as so, the widths of the column headers does not respect
the TableState data nor do they conform to the column widths of the data in the
rows below.
was:
In prior 3.x release the ExtendedDataTable control supported TableState data
for sizing of columns - this worked relatively well *however* there is/was a
bug such that the columns headers above the table did *not* align properly with
the data rows of the table below; this could be partially accommodated by
specifying a size for the column (in the TableState data) that was wider than
the longest string in the column data as he initial / minimum size.
In subsequent release (in 4.x time frame I believe) the control was refactored
and the TableState capability as a whole was lost - I saw this in another
report on the forum or Jira though not the same but other related issues may be
https://issues.jboss.org/browse/RF-4855 +
https://issues.jboss.org/browse/RF-13094 and
https://issues.jboss.org/browse/RF-13095 ; the report I remember reading,
however, is that this functionality was lost during the refactoring and was
then said to be restored in a subsequent release.
I am now using Version 5 of RichFaces to include the first milestone and latest
(overnight) snapshot and am confirming this TableState table header sizing
issue still remains, regardless of prior attempts to include TableState data
recognition and, if/as so, the widths of the column headers does not respect
the TableState data nor do they conform to the column widths of the data in the
rows below.
> ExtendedDataTable Header Column Widths does not conform to Row Data Column
> Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
> Labels: new_and_noteworthy
>
> In prior 3.x release the ExtendedDataTable control supported TableState data
> for sizing of columns - this worked relatively well *however* there is/was a
> bug such that the columns headers above the table did *not* align properly
> with the data rows of the table below; this could be partially accommodated
> by specifying a size for the column (in the TableState data) that was wider
> than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was
> refactored and the TableState capability as a whole was lost - I saw this in
> another report on the forum or Jira though not the same but other related
> issues may be https://issues.jboss.org/browse/RF-4855 +
> https://issues.jboss.org/browse/RF-13094 and
> https://issues.jboss.org/browse/RF-13095 ; the report I remember reading,
> however, is that this TableState functionality was lost during the
> refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and
> latest (overnight) snapshot and am confirming this TableState table header
> sizing issue still remains, regardless of prior attempts to include
> TableState data recognition and, if/as so, the widths of the column headers
> does not respect the TableState data nor do they conform to the column widths
> of the data in the rows below.
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
