Opened 4 years ago

Closed 4 years ago

#12741 closed bug (notabug)

JqueryUI Combobox not consistent with native browser version when using keyboard up/down keys

Reported by: AndyOfEngland Owned by:
Priority: minor Milestone: none
Component: ui.autocomplete Version: 1.11.3
Keywords: Cc:
Blocked by: Blocking:

Description

Hi,

I have had a bug raised to me regarding the keyboard functionality of the combobox.

A native browser select list works in such a way that when an item is not selected, upon mousing down into the control, the top item is highlighted and subsequent keydowns move down the option list. When an item IS selected and the user presses the down key, that is the initial item and subsequent key presses start from that point.

The JQuery enhanced version however always starts from the first item in the list.

http://jsfiddle.net/mmbzv4gb/

In the above fiddle, upon focusing into it, the keyboard (correctly) starts at the top of the list. Selecting an item, blurring away from the field and then back into it however does not function "as expected". What (I believe) should happen is that the item matching the selected in the base HTML control should be where the keyboard focus starts from.

In terms of my specific needs, ideally it would be in 2 parts - a single changeset that I can reflect in my local code (so as to get it working) and, a patch for a future update to the control.

If the above description isn't good enough, please let me know and I'll update accordingly.

Cheers

Change History (2)

comment:1 Changed 4 years ago by AndyOfEngland

In terms of why this is necessary - the control is used alongside others in a data-entry environment and consistency/speed is key for the data-entry clerks. Having to perform multiple key-presses not only takes longer for them but, it increases the risk of invalid data being keyed in.

comment:2 Changed 4 years ago by Scott González

Resolution: notabug
Status: newclosed

This is not a selectmenu, it's a demo of customizing autocomplete. The demo clearly states this is not a full widget and is not supported as such.

Note: See TracTickets for help on using tickets.