[
https://issues.jboss.org/browse/RF-11305?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11305:
------------------------------------
The clientFilterFunction is described in the showcase as follows:
{quote}
The clientFilterFunction attribute accepts a custom JavaScript function name. This
function should have two parameters; subString(current input value considering tokens) and
value (currently iterated item value) and return boolean flag which means if the value
satisfies the substring passed. The function will be called for every available suggestion
in order to construct a new list of suggestions.
{quote}
This indeed seems to be the best route to follow, as it gives developers the most
flexibility.
[rich:select] enableManualInput="true": allow search with
"contains" and not only with "startsWith"
---------------------------------------------------------------------------------------------------
Key: RF-11305
URL:
https://issues.jboss.org/browse/RF-11305
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: component-selects
Affects Versions: 4.0.0.Final
Reporter: Rene O
Assignee: Brian Leathem
Fix For: 4.1.0.Tracking
If you use rich:select with enableManualInput="true", you can only search with
the default behaviour startsWith:
Example:
http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo...
If you type: "alas" -> "Alaska" appears (search with startsWith)
but it should also be possible to achieve the same result if you type "ska"
(search with contains)
A good solution may be to control this behaviour with an extra attribute?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira