[richfaces-issues] [JBoss JIRA] Updated: (RF-7520) #{rich:component('suggestion')}.callSuggestion(true) becomes practically unusable with frequency on rich:suggestionbox

[ https://jira.jboss.org/jira/browse/RF-7520?page=com.atlassian.jira.plugin... ] Konstantin Spirov updated RF-7520: ---------------------------------- Environment: Any browser that can open Richfaces 3.3.1 showcase (was: Any browser that can open Richfaces showcase) Description: Very simple scenario to reproduce the problem: 1) Take from Richfaces showcase get RichInput:SuggestionBox:ObjectsUsageExample 2) Just add in rich:suggestionbox frequency="10" attribute 3) Recompile & redeploy 4) Click on the arrow 5) You will need to wait 10 seconds before you see the suggestion list. Please correct the problem or create an alternative method as callSuggestionASAP() There was a good idea behind .callSuggestion(true): to give us some solution to emulate the "combobox" - all delays after clicking the arrow make very bad impression, they should be minimized always when if is possible. Even without giving frequency parameter, we have default value of 400 ms. This, plus the requestDelay parameter in a4j:queue we cannot escape from, plus the time for processing the request and... the delay before diplaying the list starts to be very visible for the end user (in local network!). We need some practical alternative to skip at least the delay from "frequency". was: Very simple scenario to reproduce te problem 1) Take from Richfaces showcase get RichInput:SuggestionBox:ObjectsUsageExample 2) Just add in rich:suggestionbox frequency="10" attribute 3) Recompile & redeploy 4) Click on the arrow 5) You will need to wait 10 seconds before you see the suggestion list. Please correct the problem or create an alternative method as callSuggestionASAP() There was a good idea behind .callSuggestion(true): to give us some solution to emulate the "combobox" - all delays after clicking the arrow make very bad impression, they should be minimized always when if is possible. Even without giving frequency parameter, we have default value of 400 ms. This, plus the requestDelay parameter in a4j:queue we cannot escape from, plus the time for processing the request and... the delay before diplaying the list starts to be very visible for the end user (in local network!). We need some practical alternative to skip at least the delay from "frequency". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira