Just grabbed your latest source and was running a Siesta unit test against this. Type ahead is not working as expected. When I enter a partial match that filters the list to a single record and then press Tab, nothing is selected.

I would also recommend testing with multiple instances of the component in the same container. When typing into the last field instance and pressing tab, the record is not only not selected, but the cursor jumps to the first instance of the component.

You are right, typeAhead used to work properly ... and should work again. I still kind of losing focus as somepoint/somewhere and keyNav is unresponsive. But should need some more time to look into it.
Thanks for the report anyway
Cheers,
C.

23 May 2012, 1:56 PM

jordandev

Quote:

Originally Posted by zombeerose

Just grabbed your latest source and was running a Siesta unit test against this. Type ahead is not working as expected. When I enter a partial match that filters the list to a single record and then press Tab, nothing is selected.

I would also recommend testing with multiple instances of the component in the same container. When typing into the last field instance and pressing tab, the record is not only not selected, but the cursor jumps to the first instance of the component.

Thanks for the report.
Point 2 is fixed (still need to push to git), but can you provide a simple test case for point 1 so that I look into it (setValue/getValue are consistent with comboBox behavior in the scenarii I tested.
Cheers,
C.

The version info should be added to the head of js and css files, so that everybody can identify the right version easily.

24 May 2012, 2:28 AM

ladicek

Using keyboard

Sorry about my confusing choice of words. When I was writing about selecting by keyboard, I was actually thinking about autocomplete. So that I don't have to select from the whole (potentially huge) list, but can narrow the list down by writing into the input box. Hope you understand me :-)

I love this plugin, because its implementation is so small (which is always good), but I chose another one (roughly 5x more code!).

24 May 2012, 5:38 AM

jordandev

Quote:

Originally Posted by ladicek

Sorry about my confusing choice of words. When I was writing about selecting by keyboard, I was actually thinking about autocomplete. So that I don't have to select from the whole (potentially huge) list, but can narrow the list down by writing into the input box. Hope you understand me :-)

I love this plugin, because its implementation is so small (which is always good), but I chose another one (roughly 5x more code!).

autocomplete would be very nice

24 May 2012, 8:46 AM

zombeerose

When the component is disabled, it should not allow the cursor or typing and the triggers should not be affected.

28 May 2012, 10:45 AM

jordandev

Quote:

Originally Posted by zombeerose

When the component is disabled, it should not allow the cursor or typing and the triggers should not be affected.