[richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4
Juraj Húska (JIRA)
jira-events at lists.jboss.org
Thu Nov 14 07:11:06 EST 2013
Juraj Húska created RF-13348:
--------------------------------
Summary: pickList - columnClass attribute behaves differently than in RF4
Key: RF-13348
URL: https://issues.jboss.org/browse/RF-13348
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-selects
Affects Versions: 5.0.0.Alpha2
Reporter: Juraj Húska
{{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
Suppose a {{pickList}}, which items consist from _three_ columns.
* if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
* if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
In *RF4*, it was different though:
* it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?
--
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