[
https://issues.jboss.org/browse/RF-12493?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12493:
------------------------------------
Thanks Bernard, your changes are now much more apparent.
To be clear though, the reason you prefer adding the extra attribute over [~lfryc]'s
suggestion to change the filter function, is that you still want the filter function, you
just want to be able to control if that filter function is applied in responce to the
_onlistshow_ event.
Do we need to generalize this approach? Are there other events that do or could be
configured to trigger the application of the filter method?
Perhaps we should instead have an attribute _filterEvent_ that accepts (1 ore more) event
names at which the filter function should be applied? With a reasonable default of
course.
Add option to not filter rich:select onlistshow
-----------------------------------------------
Key: RF-12493
URL:
https://issues.jboss.org/browse/RF-12493
Project: RichFaces
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: component-input
Affects Versions: 4.2.2.Final
Reporter: Bernard Labno
Priority: Minor
Labels: waiting_on_user
Currently if we want to show all options in rich:select list despite there is already
some value typed in the input we have to add this:
onlistshow="this.rf.component.input.val('');this.rf.component.__updateItems()"
But this is usage of private method that may be subject on unexpected changes in future
releases of RF.
Add attribute to rich:select that would not filter list onlistshow.
--
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