[
https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.sy...
]
Brian Leathem commented on RF-4308:
-----------------------------------
If we resolve RichWidget issue
[#137|https://github.com/richwidgets/richwidgets/issues/137] with the proposed javascript
callback method, then the RichFaces 5 picklist CDK template could define a _data-index_
attribute, and the widget-bridge could implement a sort callback that sorted on that
_data-index_ attribute.
Using this sort would be activated by setting the _orderable = false_ facelet attribute.
rich:pickList: keep sort order of source list after add/remove
operations
-------------------------------------------------------------------------
Key: RF-4308
URL:
https://issues.jboss.org/browse/RF-4308
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 3.2.2
Reporter: Martin Höller
Labels: order, picklist, sort
Fix For: 5-Tracking
When adding items from the source list to the target list and removing this items again,
the original order of the source list is not preserved. This makes it hard to find items
in a list that is longer than just a fest items. A good example is the second example on
the livedemo at
http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the
first state (Alabama) and remove it. It can now be found at the very end of the otherwise
alphabetical list of states. This can be rather unintuitive for a user.
My suggestion is either remember the original sort order of the source list, or add some
attribute that enables automatic sorting.
--
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