[ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11995: ------------------------------- Description: 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. was: 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. <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> 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. Labels: waiting_on_user (was: ) To be clear, this problem is only observed when org.richfaces.resourceOptimization.enabled is set to true? If you disable the resourceOptimization, it works as expected? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-11995: ---------------------------------- Assignee: Juraj Huska (was: Pavol Pitonak) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.s... ] Juraj Huska reassigned RF-11995: -------------------------------- Assignee: (was: Juraj Huska) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.s... ] Juraj Huska commented on RF-11995: ---------------------------------- I can reproduce this error with showcase 4.2.1.Final on both tablets and mobile phones. The issue is noticeable only when selecting the suggestion for the first time. Then it suggest the options when 2 chars typed in. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11995?page=com.atlassian.jira.plugin.s... ] Juraj Huska updated RF-11995: ----------------------------- Affects Version/s: 4.2.1.Final (was: 4.2.0.CR1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira