]
Brian Leathem updated RF-11995:
-------------------------------
Fix Version/s: 4.3-Tracking
autocomplete only displaying select popup on minChars + 1
---------------------------------------------------------
Key: RF-11995
URL:
https://issues.jboss.org/browse/RF-11995
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-input
Affects Versions: 4.2.1.Final
Environment: Glassfish 3.1.1 / Mojarra 2.1.7 / Chrome browser
Reporter: Brendan Healey
Fix For: 4.3-Tracking
I'm running the following test with org.richfaces.resourceOptimization.enabled
set to true.
After typing the minChars number of characters (2), I see an ajax request being
sent to the server and a response is successfully returned (observed using chrome
developer tools), but the popup selection list does not appear until minChars + 1
(3) characters are entered.
Typing the third character causes a get request for combo_list_shadow.png to be
sent.
{code}
<rich:autocomplete id="findSomething"
mode="cachedAjax"
var="var"
fetchValue="#{var.name}"
minChars="2"
autocompleteMethod="#{bean.doSearch}">
<rich:column>
<h:outputText value="#{var.name}"/>
</rich:column>
</rich:autocomplete>
{code}
w
I've only just migrated to rich:autocomplete from a self-developed custom component
so I don't know if this behavior existed in any richfaces version prior to
4.2.0.CR1.
I tried this on the showcase example here:
http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocom...
(in the first autocomplete on the page) and could not reproduce the behavior.
I tried using mode="ajax" and mode="client" and could not get the
popup to show in
either case, although I'd only ever want to use cachedAjax mode normally.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: