[
https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12807109#comment-12807109
]
Brian Leathem commented on RF-13082:
------------------------------------
I made some compromises (ie. not vertically centering the picklist button
column) and this is the style rule needed to set the pick-list size:
{code}
<style type="text/css">
.pick-list .scrollBox {
max-height: 250px; // or height
}
</style>
{code}
The above css style results in a scrollbar being added to the source and target
lists when the number of elements in the respective lists is sufficiently
large. This works well in both the large and small (responsive) views. With
this re-factoring, we _could_ expose this value as a
widget-option/facelet-attribute.
{panel:bgColor=#FFFFCE}
*Note:* Setting the height of the .pick-list itself will lead to overlapping
content in responsive mode.
{panel}
> Change the orderingList component to use the new orderingList widget
> --------------------------------------------------------------------
>
> Key: RF-13082
> URL: https://issues.jboss.org/browse/RF-13082
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Attributes to be dropped in the RF5 implementation:
> * disabledClass
> * headerClass
> * itemClass
> * selectItemClass
> * listHeight
> * listWidth
> * listMaxHeight
> * listMaxWidth
> It is felt that the *Class attributes are redundant. Custom component
> styling can be achieved with the combination of the CSS class specified by
> the _styleClass_ attribute, along with the relevant stateful CSS class
> (_disabled_, _header_, _ui-selectee_, ui-selected_).
> Similarly the height/width CSS attributes are better set with CSS styles,
> rather than via facelet attributes.
> Additionally, we should consider dropping the onlist* event handlers, as
> there is considerable overlap with their on* counterparts. For instance, are
> there really use cases that require differentiating between onmouveover and
> onlistmouseover?
--
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
