[JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13348.
--------------------------------
Assignee: Brian Leathem
Resolution: Done
> 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
11 years
[JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13348:
------------------------------------
The _columnClasses_ attribute doc describes the fix implemented:
{quote}
_columnClasses_ specifies a comma-delimited list of CSS style classes to apply to each column.
A space separated list of classes may be specified for an individual column.
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.
If there are more class names than columns, the overflow ones are ignored.
{quote}
> 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
> 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
11 years
[JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13348:
-------------------------------
Fix Version/s: 5.0.0.Alpha2
> 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
> 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
11 years
[JBoss JIRA] (RF-13172) rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13172:
-------------------------------
Labels: low_hanging_fruit needs-qe (was: low_hanging_fruit)
> rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
> ------------------------------------------------------------------------------------------------------------
>
> Key: RF-13172
> URL: https://issues.jboss.org/browse/RF-13172
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.3
> Reporter: Sergey Zubarev
> Assignee: Pavel Slegr
> Labels: low_hanging_fruit, needs-qe
> Fix For: 4.3.5
>
>
> {code}
> <rich:toolbar itemSeparator="line" id="repairWorkToolbar">
> <rich:toolbarGroup>
> <a4j:commandLink value="btn1"/>
> <a4j:commandLink value="btn2"/>
> <a4j:commandLink value="btn3" *rendered="false"*/>
> </rich:toolbarGroup>
> <rich:toolbarGroup location="right">
> <a4j:commandLink value="btn_right"/>
> </rich:toolbarGroup>
> ...
> {code}
> In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine.
> Html debug shows, that code produced one extra element in colgroup tag when using rendered="false".
--
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
11 years
[JBoss JIRA] (RF-13172) rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13172:
-------------------------------
Fix Version/s: 4.3.5
(was: 5-Tracking)
> rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
> ------------------------------------------------------------------------------------------------------------
>
> Key: RF-13172
> URL: https://issues.jboss.org/browse/RF-13172
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.3
> Reporter: Sergey Zubarev
> Assignee: Pavel Slegr
> Labels: low_hanging_fruit
> Fix For: 4.3.5
>
>
> {code}
> <rich:toolbar itemSeparator="line" id="repairWorkToolbar">
> <rich:toolbarGroup>
> <a4j:commandLink value="btn1"/>
> <a4j:commandLink value="btn2"/>
> <a4j:commandLink value="btn3" *rendered="false"*/>
> </rich:toolbarGroup>
> <rich:toolbarGroup location="right">
> <a4j:commandLink value="btn_right"/>
> </rich:toolbarGroup>
> ...
> {code}
> In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine.
> Html debug shows, that code produced one extra element in colgroup tag when using rendered="false".
--
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
11 years