[richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4

Juraj Húska (JIRA) jira-events at lists.jboss.org
Mon Nov 25 08:54:07 EST 2013


     [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj Húska reopened RF-13348:
------------------------------



I am reopening the issue, because it is not behaving as the doc describes.

IMHO it is a bug and that the doc is correct.

It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns

* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column

Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout.xhtml
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.

My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be
applied to the columns greater than the number of classes. If however the final class in the list is the `*`
character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order
the class in this list.

It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
                
> 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
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{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