Selectmenu Widgetversion added: 1.0
Description: Creates a select menu widget
The select menu is based on a native select element, which is hidden from view and replaced with a custom-styled select button that matches the look and feel of the jQuery Mobile framework. The select menu is ARIA-enabled and keyboard accessible on the desktop as well.
By default, the framework leverages the native OS options menu to use with the custom button. When the button is clicked, the native OS menu will open. When a value is selected and the menu closes, the custom button's text is updated to match the selected value. Please note that the framework also offers the possibility of having custom (non-native) select menus.
To add a select menu to your page, start with a standard select
element populated with a set of option
elements. Set the for
attribute of the label
to match the id
of the select
so they are semantically associated. It's possible to accessibly hide the label if it's not desired in the page layout, but we require that it is present in the markup for semantic and accessibility reasons.
The framework will find all select
elements and automatically enhance them into select menus, no need to apply a data-role
attribute. To prevent the automatic enhancement of a select, add data-role="none"
attribute to the select
.
1
2
3
4
5
6
7
|
|
This will produce a basic select menu. The default styles set the width of the input to 100% of the parent container and stacks the label on a separate line.
Mini version
For a more compact version that is useful in toolbars and tight spaces, add the data-mini="true"
attribute to the element to create a mini version.
1
2
3
4
5
6
7
|
|
This will produce a select that a not as tall as the standard version and has a smaller text size.
Field containers
Optionally wrap the selects in a container with class ui-field-contain
to help visually group it in a longer form.
Note: The data-
attribute data-role="fieldcontain"
is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Add class ui-field-contain
instead.
1
2
3
4
5
6
7
8
9
|
|
The select input is now displayed like this:
An example of a select with a long list of options:
Optgroups
The following example organizes the options into optgroup
elements. Support for this feature in mobile selects is a bit spotty, but is improving.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
|
Vertically grouped select inputs
To create a grouped set of select inputs, first add select
and a corresponding label
. Set the for
attribute of the label
to match the id
of the select
so they are semantically associated.
Because the label
element will be associated with each individual select input and will be hidden for styling purposes, we recommend wrapping the selects in a fieldset
element that has a legend
which acts as the combined label for the grouped inputs.
Lastly, one needs to wrap the fieldset
in a div
with data-role="controlgroup"
attribute, so it can be styled as a group.
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
|
|
Horizontally grouped select inputs
Select inputs can also be used for grouped sets with more than one related selections. To make a horizontal button set, add the data-type="horizontal"
to the fieldset. Note that the buttons which trigger the select will resize depending on the currently selected option’s value.
1
|
|
Theming selects
You can specify any jQuery Mobile button data-
attribute on a select element, too. In this example, we're setting the theme, icon and inline properties:
Custom select menus
The framework is capable of building a custom menu based on the select
element's list of options. We recommend using a custom menu when multiple selections are required, or when the menu itself must be styled with CSS.
You can optionally use custom-styled select menus instead of the native OS menu. The custom menu supports disabled options and multiple selection (whereas native mobile OS support for both is inconsistent), adds an elegant way to handle placeholder values, and restores missing functionality on certain platforms such as optgroup
support on Android (all explained below). In addition, the framework applies the custom button's theme to the menu to better match the look and feel and provide visual consistency across platforms. Lastly, custom menus often look better on desktop browsers because native desktop menus are smaller than their mobile counterparts and tend to look disproportionate.
Keep in mind that there is overhead involved in parsing the native select to build a custom menu. If there are a lot of selects on a page, or a select has a long list of options, this can impact the performance of the page, so we recommend using custom menus sparingly.
To use custom menus on a specific select
, just add the data-native-menu="false"
attribute. Alternately, this can also programmatically set the select menu's nativeMenu
configuration option to false
in a callback bound to the mobileinit
event to achieve the same effect. This will globally make all selects use the custom menu by default. The following must be included in the page after jQuery is loaded but before jQuery Mobile is loaded.
1
2
3
|
|
When the select
has a small number of options that will fit on the device's screen, the menu will appear as a small overlay with a pop transition:
When it has too many options to show on the device's screen, the framework will automatically create a new dialog-style "page" populated with a standard listview for the options. This allows us to use the native scrolling included on the device for moving through a long list. The text inside the label
is used as the title for this page. Be aware of the page and pagecontainer events that will be fired for this generated page.
Note: The behavior whereby the custom select menu creates a new page when the list of options is long is deprecated as of jQuery Mobile 1.4.0. Starting with 1.5.0, the custom select menu will fall back to utilizing the select menu's native behavior when the list of options is too long.
Disabled options
jQuery Mobile will automatically disable and style option tags with the disabled
attribute. In the demo below, the second option "Rush: 3 days" has been set to disabled.
Placeholder options
It's common for developers to include a "null" option in their select element to force a user to choose an option. If a placeholder option is present in your markup, jQuery Mobile will hide them in the overlay menu, showing only valid choices to the user, and display the placeholder text inside the menu as a header. A placeholder option is added when the framework finds:
- An option with no value attribute
- An option with an empty value attribute (
value=""
).Note: Indicating that an option should be used as a placeholder by providing the
value
attribute and setting it to "" is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. - An option with no text node
- An option with a
data-placeholder="true"
attribute. (This allows you to use an option that has a value and a textnode as a placeholder option).
You can disable this feature through the selectmenu plugin's hidePlaceholderMenuItems
option, like this:
1
|
|
Examples of various placeholder options:
Multiple selects
If the multiple
attribute is present in your markup, jQuery Mobile will enhance the element with a few extra considerations:
- A header element will be created inside the menu and display the placeholder text and a close button.
- Clicking on an item inside the overlay menu will not close the widget.
- A ghosted, unchecked icon will appear adjacent to each unselected item. When the item is selected the icon will change to a checkbox. Neither icon will appear inside a single select box.
- Once 2+ items are selected, a counter element with the total number of selected items will appear inside the button.
- The text of each selected item will appear inside the button as a list. If the button is not wide enough to display the entire list, it is truncated with an ellipses.
- If no items are selected, the button's text will default to the placeholder text.
- If no placeholder element exists, the default button text will be blank and the header will appear with just a close button. Because this isn't a friendly user experience, we recommended that you always specify a placeholder element when using multiple select boxes.
- Currently jQuery Mobile only supports the
multiple
attribute on aselect
withnativeMenu
set tofalse
.
When a select is large enough to where the menu will open in a new page, the placeholder text is displayed in the button when no items are selected, and the label
text is displayed in the menu's header. This differs from smaller overlay menus where the placeholder text is displayed in both the button and the header, and from full-page single selects where the placeholder text is not used at all.
Optgroup support
If a select menu contains optgroup
elements, jQuery Mobile will create a divider & group items based on the label
attribute's text:
Theming selects
You can specify any jQuery Mobile button data-
attribute on a select element, too. In this example, we're setting the theme, icon and inline properties:
The data-overlay-theme
attribute can be added to a select element to set the color of the overlay layer for the dialog-based custom select menus and the outer border of the smaller custom menus. By default, the content block colors for swatch "a" will be used for the overlays.
Note: Custom selects use the popup widget for the menu. Because the popup container is elsewhere on the page it can't inherit the theme swatch from the parent of the select, and inherits from the page instead.
Calling the select menu plugin
The select menu plugin will auto initialize on any page that contains a select menu, without any need for a data-role
attribute in the markup. However, you can directly call the select menu plugin on any selector, just like any normal jQuery plugin:
1
|
|
ID generation
The selectmenu widget adds an ID to the elements it generates. If it doesn't itself have an ID, it will use a prefix consisting of select-
and a unique number for the elements. If it does have an ID, it will use its ID as the prefix. The ID for the various elements generated by the selectmenu widget is then constructed as follows:
- button
-
<prefix>-button
- popup
-
<prefix>-listbox
This id is only assigned to an element when the selectmenu widget is constructed with the option
nativeMenu
set tofalse
.Since the menu is implemented as a popup it will assign IDs to its generated elements. See the popup widget's id generation for details.
- listview
-
<prefix>-menu
This id is only assigned to an element when the selectmenu widget is constructed with the option
nativeMenu
set tofalse
.
For example, creating a non-native selectmenu with
1
2
3
4
5
6
|
|
will result in the following markup:
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
29
30
31
32
33
34
|
|
Options
closeText
"Close"
Customizes the text of the close button which is helpful for translating this into different languages. The close button is displayed as an icon-only button by default so the text isn't visible on-screen, but is read by screen readers so this is an important accessibility feature.
This option is also exposed as a data attribute: data-close-text="Fermer"
.
Initialize the selectmenu with the closeText
option specified:
1
2
3
|
|
Get or set the closeText
option, after initialization:
1
2
3
4
5
|
|
corners
true
This option is also exposed as a data attribute: data-corners="false"
.
Initialize the selectmenu with the corners
option specified:
1
2
3
|
|
Get or set the corners
option, after initialization:
1
2
3
4
5
|
|
defaults
false
true
indicates that other widgets options have default values and causes jQuery Mobile's widget autoenhancement code to omit the step where it retrieves option values from data attributes. This can improve startup time.
This option is also exposed as a data attribute: data-defaults="true"
.
Initialize the selectmenu with the defaults
option specified:
1
2
3
|
|
Get or set the defaults
option, after initialization:
1
2
3
4
5
|
|
disabled
false
true
.
This option is also exposed as a data attribute: data-disabled="true"
.
Initialize the selectmenu with the disabled
option specified:
1
2
3
|
|
Get or set the disabled
option, after initialization:
1
2
3
4
5
|
|
dividerTheme
null, inherited from parent
optgroup
headers. It accepts a single letter from a-z that maps to the swatches included in your theme.
Possible values: swatch letter (a-z).
This option is also exposed as a data attribute: data-divider-theme="b"
.
Initialize the selectmenu with the dividerTheme
option specified:
1
2
3
|
|
Get or set the dividerTheme
option, after initialization:
1
2
3
4
5
|
|
hidePlaceholderMenuItems
true
This option is also exposed as a data attribute: data-hide-placeholder-menu-items="false"
.
Initialize the selectmenu with the hidePlaceholderMenuItems
option specified:
1
2
3
|
|
Get or set the hidePlaceholderMenuItems
option, after initialization:
1
2
3
4
5
|
|
icon
"carat-d"
To suppress the icon, a boolean expression must be used:
This option is also exposed as a data attribute: data-icon="star"
.
Initialize the selectmenu with the icon
option specified:
1
2
3
|
|
Get or set the icon
option, after initialization:
1
2
3
4
5
|
|
iconpos
"right"
This option is also exposed as a data attribute: data-iconpos="left"
.
Initialize the selectmenu with the iconpos
option specified:
1
2
3
|
|
Get or set the iconpos
option, after initialization:
1
2
3
4
5
|
|
iconshadow
true
Applies the theme shadow to the select button's icon if set to true.
This option is also exposed as a data attribute: data-iconshadow="false"
.
Initialize the selectmenu with the iconshadow
option specified:
1
2
3
|
|
Get or set the iconshadow
option, after initialization:
1
2
3
4
5
|
|
initSelector
See below
The default initSelector
for the selectmenu widget is:
1
|
|
Note: This option is deprecated in 1.4.0 and will be removed in 1.5.0.
As of jQuery Mobile 1.4.0, the initSelector
is no longer a widget option. Instead, it is declared directly on the widget prototype. Thus, you may specify a custom value by handling the mobileinit
event and overwriting the initSelector
on the prototype:
1
2
3
|
|
Note: Remember to attach the mobileinit
handler after you have loaded jQuery, but before you load jQuery Mobile, because the event is triggered as part of jQuery Mobile's loading process.
The value of this option is a jQuery selector string. The framework selects elements based on the value of this option and instantiates selectmenu widgets on each of the resulting list of elements.
(version deprecated: 1.4.0)inline
null (false)
This option is also exposed as a data attribute: data-inline="true"
.
Initialize the selectmenu with the inline
option specified:
1
2
3
|
|
Get or set the inline
option, after initialization:
1
2
3
4
5
|
|
mini
null (false)
true
, this will display a more compact version of the selectmenu that uses less vertical height by applying the ui-mini
class to the outermost element of the selectmenu widget.
This option is also exposed as a data attribute: data-mini="true"
.
nativeMenu
true
This option is also exposed as a data attribute: data-native-menu="false"
.
Initialize the selectmenu with the nativeMenu
option specified:
1
2
3
|
|
Get or set the nativeMenu
option, after initialization:
1
2
3
4
5
|
|
overlayTheme
"null, inherited from parent"
This option is also exposed as a data attribute: data-overlay-theme="a"
.
Initialize the selectmenu with the overlayTheme
option specified:
1
2
3
|
|
Get or set the overlayTheme
option, after initialization:
1
2
3
4
5
|
|
preventFocusZoom
true on iOS platforms
This option is also exposed as a data attribute: data-prevent-focus-zoom="true"
.
Initialize the selectmenu with the preventFocusZoom
option specified:
1
2
3
|
|
Get or set the preventFocusZoom
option, after initialization:
1
2
3
4
5
|
|
shadow
true
This option is also exposed as a data attribute: data-shadow="false"
.
Initialize the selectmenu with the shadow
option specified:
1
2
3
|
|
Get or set the shadow
option, after initialization:
1
2
3
4
5
|
|
theme
null, inherited from parent
Possible values: swatch letter (a-z).
This option is also exposed as a data attribute: data-theme="b"
.
Initialize the selectmenu with the theme
option specified:
1
2
3
|
|
Get or set the theme
option, after initialization:
1
2
3
4
5
|
|
Methods
close()Returns: jQuery (plugin only)
- 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
|
|
open()Returns: jQuery (plugin only)
- This method does not accept any arguments.
Invoke the open method:
1
|
|
option( optionName )Returns: Object
optionName
.-
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)
optionName
.-
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
|
|
refresh()Returns: jQuery (plugin only)
This is used to update the custom select to reflect the native select element's value. If the number of options in the select are different than the number of items in the custom menu, it'll rebuild the custom menu.
- This signature does not accept any arguments.
Invoke the method:
1
|
|
refresh( option )Returns: jQuery (plugin only)
This is used to update the custom select to reflect the native select element's value. If the number of options in the select are different than the number of items in the custom menu, it'll rebuild the custom menu. If you pass a true argument you can force the rebuild to happen.
-
optionType: Booleanto force a rebuild
Invoke the method:
1
|
|
Events
create( event, ui )Type: selectcreate
Note: The ui
object is empty but included for consistency with other events.
Initialize the selectmenu with the create callback specified:
1
2
3
|
|
Bind an event listener to the selectcreate event:
1
|
|
Example:
A basic example of a simple native select
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
29
|
|