[
https://issues.jboss.org/browse/RF-10227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12813809#comment-12813809
]
Lukáš Fryč commented on RF-10227:
---------------------------------
1) Event update allows to intercept autocompletion and read a list of available
suggestions
2) Some counter-examples for not showing {{There are no suggestions}}: Google
autocomplete, autocompletion built into browsers.
3) The other problem is that Autocomplete doesn't indicate whether suggestion
mechanism is in progress, fortunately you can use r:status to show progress to
an user. It is then evident from the status, that when there are no suggestions
after completion, nothing is available.
Just to clarify, I'm not saying we shouldn't implement it, just brain-storming
possible options. ;-)
Note that we will need this functionality for RF5 r:select, which means that we
could share functionality with r:autocomplete.
> autocomplete: implement "nothingLabel"
> --------------------------------------
>
> Key: RF-10227
> URL: https://issues.jboss.org/browse/RF-10227
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: base functionality, component-input
> Affects Versions: 4.0.0.Milestone5
> Reporter: Juergen Zimmermann
> Fix For: 5-Future
>
>
> rich:autocomplete doesn't have an attribute for a "nothingLabel" to indicate
> that there are no matches
--
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