rich:autocomplete popup selection box freezing
wrdlprmpft Jun 14, 2013 6:31 AMDear Richfaces Community
I have a very critical problem with rich:autocomplete. I am not sure, whether this is a similar issue as described herein. I tried the work around described, but it is not working for me.
I have a component with four autocomplete fields, accompanying clear buttons and labels. Currently I test with following options: autofill="false", showButton="true", mode="cachedAjax". As a workaround for issue RF-12152 I use a javascript filling an empty space onfocus (onfocus="#{rich:component('region')}.setValue(' ');"). The backing bean logic is, that the autocomplete method takes into account all input also from the other fields to filter the selction shown in the popup drop down menu.
Now if I try to use it, I can make a selection in the first box. When I get to the second box I observe two kinds of misbehaviours:
1.) Mostly the popup completely freezes. The select highlighting is not shown at all or it is frozen to one item, it is not possible to select an item and the popup does not close any more. If you point to an item you can get the text marked, which is not the normal behaviour. Nothing is selected, the popup does not close. You see this in the following screenshot:
Partly this issue seems to be due to a great delay in rendering. In some cases the select highlighting comes back and I can select then an item. In these cases it mostly happens, that the popup with the selected item freezes again as shown below:
As browser I am using Firefox 21.0.
The number of items to be displayed in the first example (Bayern) is seven. In the second example (Baden-Württemberg) it is four. There seems indication, that the small difference in these small number of items causes great differences in the delay. It is more likely to get it finally free for item slection in the second case with only four items. I never experineced such problem with the same application logic in Richfaces 3 components suggestionbox or combobox.
Is this a known issue. Any recommendations for work arounds?
Kind regards and thanks in advance
Chris
Below is the full xhtml code: