Autocomplete Widgetversion added: 1.8
Description: Autocomplete enables users to quickly find and select from a pre-populated list of values as they type, leveraging searching and filtering.
Any field that can receive input can be converted into an Autocomplete, namely, <input>
elements, <textarea>
elements, and elements with the contenteditable
attribute.
When typing in the autocomplete field, the plugin starts searching for entries that match and displays a list of values to choose from. By entering more characters, the user can filter down the list to better matches.
This can be used to choose previously selected values, such as entering tags for articles or entering email addresses from an address book. Autocomplete can also be used to populate associated information, such as entering a city name and getting the zip code.
You can pull data in from a local or remote source: Local is good for small data sets, e.g., an address book with 50 entries; remote is necessary for big data sets, such as a database with hundreds or millions of entries to select from. To find out more about customizing the data source, see the documentation for the source
option.
Keyboard interaction
When the menu is open, the following key commands are available:
-
UP
: Move focus to the previous item. If on first item, move focus to the input. If on the input, move focus to last item. -
DOWN
: Move focus to the next item. If on last item, move focus to the input. If on the input, move focus to the first item. -
ESCAPE
: Close the menu. -
ENTER
: Select the currently focused item and close the menu. -
TAB
: Select the currently focused item, close the menu, and move focus to the next focusable element. -
PAGE UP
/PAGE DOWN
: Scroll through a page of items (based on height of menu). It's generally a bad idea to display so many items that users need to page.
When the menu is closed, the following key commands are available:
-
UP
/DOWN
: Open the menu, if theminLength
has been met.
Theming
The autocomplete widget uses the jQuery UI CSS framework to style its look and feel. If autocomplete specific styling is needed, the following CSS class names can be used for overrides or as keys for the classes
option:
-
ui-autocomplete
: The menu used to display matches to the user. -
ui-autocomplete-input
: The input element that the autocomplete widget was instantiated with. While requesting data to display to the user, theui-autocomplete-loading
class is also added to this element.
Dependencies
Additional Notes:
- This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.
-
This widget manipulates its element's value programmatically, therefore a native
change
event may not be fired when the element's value changes.
Options
appendTo
null
Which element the menu should be appended to. When the value is null
, the parents of the input field will be checked for a class of ui-front
. If an element with the ui-front
class is found, the menu will be appended to that element. Regardless of the value, if no element is found, the menu will be appended to the body.
appendTo
option should not be changed while the suggestions menu is open.Initialize the autocomplete with the appendTo
option specified:
1
2
3
|
|
Get or set the appendTo
option, after initialization:
1
2
3
4
5
|
|
autoFocus
false
true
the first item will automatically be focused when the menu is shown.Initialize the autocomplete with the autoFocus
option specified:
1
2
3
|
|
Get or set the autoFocus
option, after initialization:
1
2
3
4
5
|
|
classes
{}
Specify additional classes to add to the widget's elements. Any of classes specified in the Theming section can be used as keys to override their value. To learn more about this option, check out the learn article about the classes
option.
Initialize the autocomplete with the classes
option specified, changing the theming for the ui-autocomplete
class:
1
2
3
4
5
|
|
Get or set a property of the classes
option, after initialization, here reading and changing the theming for the ui-autocomplete
class:
1
2
3
4
5
|
|
delay
300
Initialize the autocomplete with the delay
option specified:
1
2
3
|
|
Get or set the delay
option, after initialization:
1
2
3
4
5
|
|
disabled
false
true
.Initialize the autocomplete with the disabled
option specified:
1
2
3
|
|
Get or set the disabled
option, after initialization:
1
2
3
4
5
|
|
minLength
1
Initialize the autocomplete with the minLength
option specified:
1
2
3
|
|
Get or set the minLength
option, after initialization:
1
2
3
4
5
|
|
position
{ my: "left top", at: "left bottom", collision: "none" }
of
option defaults to the input element, but you can specify another element to position against. You can refer to the jQuery UI Position utility for more details about the various options.Initialize the autocomplete with the position
option specified:
1
2
3
|
|
Get or set the position
option, after initialization:
1
2
3
4
5
|
|
source
none; must be specified
Independent of the variant you use, the label is always treated as text. If you want the label to be treated as html you can use Scott González' html extension. The demos all focus on different variations of the source
option - look for one that matches your use case, and check out the code.
-
Array:
An array can be used for local data. There are two supported formats:
- An array of strings:
[ "Choice1", "Choice2" ]
- An array of objects with
label
andvalue
properties:[ { label: "Choice1", value: "value1" }, ... ]
value
properties, the value will also be used as the label. - An array of strings:
-
String: When a string is used, the Autocomplete plugin expects that string to point to a URL resource that will return JSON data. It can be on the same host or on a different one (must provide JSONP). The Autocomplete plugin does not filter the results, instead a query string is added with a
term
field, which the server-side script should use for filtering the results. For example, if thesource
option is set to"http://example.com"
and the user typesfoo
, a GET request would be made tohttp://example.com?term=foo
. The data itself can be in the same format as the local data described above. -
Function:
The third variation, a callback, provides the most flexibility and can be used to connect any data source to Autocomplete. The callback gets two arguments:
- A
request
object, with a singleterm
property, which refers to the value currently in the text input. For example, if the user enters"new yo"
in a city field, the Autocomplete term will equal"new yo"
. - A
response
callback, which expects a single argument: the data to suggest to the user. This data should be filtered based on the provided term, and can be in any of the formats described above for simple local data. It's important when providing a custom source callback to handle errors during the request. You must always call theresponse
callback even if you encounter an error. This ensures that the widget always has the correct state.
When filtering data locally, you can make use of the built-in
$.ui.autocomplete.escapeRegex
function. It'll take a single string argument and escape all regex characters, making the result safe to pass tonew RegExp()
. - A
Initialize the autocomplete with the source
option specified:
1
2
3
|
|
Get or set the source
option, after initialization:
1
2
3
4
5
|
|
Methods
close()Returns: jQuery (plugin only)
search
method, to close the open menu.- This method does not accept any arguments.
Invoke the close method:
1
|
|
destroy()Returns: jQuery (plugin only)
- This method does not accept any arguments.
Invoke the destroy method:
1
|
|
disable()Returns: jQuery (plugin only)
- This method does not accept any arguments.
Invoke the disable method:
1
|
|
enable()Returns: jQuery (plugin only)
- This method does not accept any arguments.
Invoke the enable method:
1
|
|
instance()Returns: Object
Retrieves the autocomplete's instance object. If the element does not have an associated instance, undefined
is returned.
Unlike other widget methods, instance()
is safe to call on any element after the autocomplete plugin has loaded.
- This method does not accept any arguments.
Invoke the instance method:
1
|
|
option( optionName )Returns: Object
Gets the value currently associated with the specified optionName
.
Note: For options that have objects as their value, you can get the value of a specific key by using dot notation. For example, "foo.bar"
would get the value of the bar
property on the foo
option.
-
optionNameType: StringThe name of the option to get.
Invoke the method:
1
|
|
option()Returns: PlainObject
- This signature does not accept any arguments.
Invoke the method:
1
|
|
option( optionName, value )Returns: jQuery (plugin only)
Sets the value of the autocomplete option associated with the specified optionName
.
Note: For options that have objects as their value, you can set the value of just one property by using dot notation for optionName
. For example, "foo.bar"
would update only the bar
property of the foo
option.
-
optionNameType: StringThe name of the option to set.
-
valueType: ObjectA value to set for the option.
Invoke the method:
1
|
|
option( options )Returns: jQuery (plugin only)
-
optionsType: ObjectA map of option-value pairs to set.
Invoke the method:
1
|
|
search( [value ] )Returns: jQuery (plugin only)
search
event and invokes the data source if the event is not canceled. Can be used by a selectbox-like button to open the suggestions when clicked. When invoked with no parameters, the current input's value is used. Can be called with an empty string and minLength: 0
to display all items.-
valueType: String
Invoke the search method:
1
|
|
widget()Returns: jQuery
jQuery
object containing the menu element. Although the menu items are constantly created and destroyed, the menu element itself is created during initialization and is constantly reused.- This method does not accept any arguments.
Invoke the widget method:
1
|
|
Extension Points
The autocomplete widget is built with the widget factory and can be extended. When extending widgets, you have the ability to override or add to the behavior of existing methods. The following methods are provided as extension points with the same API stability as the plugin methods listed above. For more information on widget extensions, see Extending Widgets with the Widget Factory.
_renderItem( ul, item )Returns: jQuery
Method that controls the creation of each option in the widget's menu. The method must create a new <li>
element, append it to the menu, and return it.
-
ulType: jQueryThe
<ul>
element that the newly created<li>
element must be appended to. -
itemType: Object
Add the item's value as a data attribute on the <li>
.
1
2
3
4
5
6
|
|
_renderMenu( ul, items )Returns: jQuery (plugin only)
<ul>
and an array of items that match the user typed term. Creation of the individual <li>
elements should be delegated to _renderItemData()
, which in turn delegates to the _renderItem()
extension point.
-
ulType: jQueryAn empty
<ul>
element to use as the widget's menu. -
itemsType: ArrayAn Array of items that match the user typed term. Each item is an Object with
label
andvalue
properties.
Add a CSS class name to the odd menu items.
1
2
3
4
5
6
7
|
|
_resizeMenu()Returns: jQuery (plugin only)
this.menu.element
.- This method does not accept any arguments.
Always display the menu as 500 pixels wide.
1
2
3
|
|
Events
change( event, ui )Type: autocompletechange
-
eventType: Event
-
uiType: Object
-
itemType: ObjectThe item selected from the menu, if any. Otherwise the property is
null
.
-
Initialize the autocomplete with the change callback specified:
1
2
3
|
|
Bind an event listener to the autocompletechange event:
1
|
|
close( event, ui )Type: autocompleteclose
close
event will be accompanied by a change
event.Note: The ui
object is empty but included for consistency with other events.
Initialize the autocomplete with the close callback specified:
1
2
3
|
|
Bind an event listener to the autocompleteclose event:
1
|
|
create( event, ui )Type: autocompletecreate
Note: The ui
object is empty but included for consistency with other events.
Initialize the autocomplete with the create callback specified:
1
2
3
|
|
Bind an event listener to the autocompletecreate event:
1
|
|
focus( event, ui )Type: autocompletefocus
Canceling this event prevents the value from being updated, but does not prevent the menu item from being focused.
Initialize the autocomplete with the focus callback specified:
1
2
3
|
|
Bind an event listener to the autocompletefocus event:
1
|
|
open( event, ui )Type: autocompleteopen
Note: The ui
object is empty but included for consistency with other events.
Initialize the autocomplete with the open callback specified:
1
2
3
|
|
Bind an event listener to the autocompleteopen event:
1
|
|
response( event, ui )Type: autocompleteresponse
source
option callback is not required. This event is always triggered when a search completes, even if the menu will not be shown because there are no results or the Autocomplete is disabled.-
eventType: Event
-
uiType: Object
-
contentType: ArrayContains the response data and can be modified to change the results that will be shown. This data is already normalized, so if you modify the data, make sure to include both
value
andlabel
properties for each item.
-
Initialize the autocomplete with the response callback specified:
1
2
3
|
|
Bind an event listener to the autocompleteresponse event:
1
|
|
search( event, ui )Type: autocompletesearch
minLength
and delay
are met. If canceled, then no request will be started and no items suggested.Note: The ui
object is empty but included for consistency with other events.
Initialize the autocomplete with the search callback specified:
1
2
3
|
|
Bind an event listener to the autocompletesearch event:
1
|
|
select( event, ui )Type: autocompleteselect
Canceling this event prevents the value from being updated, but does not prevent the menu from closing.
-
eventType: Event
-
uiType: Object
-
itemType: ObjectAn Object with
label
andvalue
properties for the selected option.
-
Initialize the autocomplete with the select callback specified:
1
2
3
|
|
Bind an event listener to the autocompleteselect event:
1
|
|
Examples:
A simple jQuery UI Autocomplete
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
|
Demo:
Using a custom source callback to match only the beginning of terms
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
|