I have a problem with comboboxes. the following situation occurs:
I have a combo box with a lot (up to 100) selectable items. The combobox is filled using a BeanItemContainer and the NullSelectionAllowed is set to false. Scrolling and selection of items work fine.
Only if I execute the next sequence of actions something strange happens:
click on the arrow of the combobox to extend the list (drop down the list). The initial selected is still in the field.
click on the arrow at the bottom of the list (to scroll to the next 10 items in the list). The initial selected item is stil in the field.
click anywhere in the screen accept on the list. This results in an empty field.
I would expect the inital selected value is still in the field. The user didn’t select anything, so no changes in value are expected.
I have no idea where to look or how to slove this. Any pointers are welcome.
Can be reproduced in
Vaadin Sampler . It doesn’t seem to fire a ValueChangeEvent, the caption for the selected item just seems to disappear. It comes back by just opening the combobox. Seems like a bug.
We have an issue with a combobox with many items. If you have the combobox expanded and press and hold the page down button, eventually there start to appear blank pages. If you back up, by clicking, and re-enter the same page the entries are there. With debug on (see below) notice that “page (i) : 30” is duplicated for a blank page. We’re using Vaadin 6.6.6 and my browser is firefox 3.6.23. Any ideas? Is this possibly a known issue?
change
LOADING
Processing time was 25ms for 779 characters of JSON
Referenced paintables: 316
Variable burst to be sent to server:
PID425 (class com.vaadin.terminal.gwt.client.ui.VFilterSelect) :
filter (s) :
page (i) : 28
Making UIDL Request with params: 52b7156c-017c-464d-a4cc-d495663f18e4 PID425 filter s 28 PID425 page i
Server visit took 33ms
JSON parsing took 0ms
change
LOADING
Processing time was 25ms for 779 characters of JSON
Referenced paintables: 316
Variable burst to be sent to server:
PID425 (class com.vaadin.terminal.gwt.client.ui.VFilterSelect) :
filter (s) :
page (i) : 29
Making UIDL Request with params: 52b7156c-017c-464d-a4cc-d495663f18e4 PID425 filter s 29 PID425 page i
Server visit took 62ms
JSON parsing took 1ms
change
LOADING
Processing time was 49ms for 779 characters of JSON
Referenced paintables: 316
Variable burst to be sent to server:
PID425 (class com.vaadin.terminal.gwt.client.ui.VFilterSelect) :
filter (s) :
page (i) : 30
Making UIDL Request with params: 52b7156c-017c-464d-a4cc-d495663f18e4 PID425 filter s 30 PID425 page i
Server visit took 79ms
JSON parsing took 0ms
change
LOADING
Processing time was 51ms for 779 characters of JSON
Referenced paintables: 316
Variable burst to be sent to server:
PID425 (class com.vaadin.terminal.gwt.client.ui.VFilterSelect) :
filter (s) :
page (i) : 30
Making UIDL Request with params: 52b7156c-017c-464d-a4cc-d495663f18e4 PID425 filter s 30 PID425 page i
Server visit took 77ms
JSON parsing took 1ms
change
LOADING
Processing time was 26ms for 779 characters of JSON
Referenced paintables: 316
Please don’t hijack old threads. The previously discussed issue was resolved over a year ago.
You reported issue seems to be similar to
http://dev.vaadin.com/ticket/7257 with the only difference being whether arrow down or page down is used to quickly scroll through the suggestion list.