#

Navigation Search

- Accordion
- AJAX Navigation
- Autocomplete
- Buttons
- Checkboxes
- Collapsibles
- Controlgroup
- Dialogs
- Fixed toolbars
- Flip switch toggle
- Footer toolbar
- Form elements
- Grids
- Header toolbar
- Icons
- Links
- Listviews
- Loader overlay
- Navbar
- Navbar, persistent
- Pages
- Panels New
- Popup
- Radio buttons
- Select
- Slider, single
- Slider, dual range New
- Table, column toggle New
- Table, reflow New
- Text inputs & textarea
- Transitions
- Collapsibles
- Dynamic collapsible
- Controlgroups
- Dynamic controlgroup
- Listviews
- Grid Listview
- Autodividers Linkbar
- Autodividers Selector
- Navigation
- Backbone and Require.js example
- Redirection with server-side support
- Panels
- Panel styling
- Open panel on swipe
- Popups
- Dynamic popup
- Popup with arrow
- Responsive Tables
- Reflow: Custom styles
- Reflow: Heading groups
- Reflow: Refresh method
- Column toggle: Customization options
- Column toggle: Heading groups
- Column toggle: Refresh method
- Column toggle demo: Phone comparison
- Sliders
- Tooltip extension
- Swipe
- Swipe to navigate
- Swipe to delete list item
- Forms
- Why won't my CSS styles apply correctly to a widget?
- Updating the value of enhanced form elements does not work.
- My HTML 5 inputs look different across devices and browsers.
- My range or search inputs are being change to number/text.
- Sometimes my custom select shows as a popup other times its a dialog.
- Disabling a button does not work.
- Controls in my fixed header or footer are not responding or behave erratically.
- Pages
- Why aren't my scripts and styles loading?
- Why isn't DOM ready working for my scripts?
- How do I load a page?
- Why is only the first page of my multi page document loaded?
- I'm trying to pass query params to a page but it's not working?
- I'm trying to pass information via the hash but it's not working?
- I'm trying to use the application cache but it's not working.
- Content injected into a page is not enhanced.
- Triggering create on injected HTML does not work.
- How can I stop JQM from auto-enhancing an element?
- How can I stop JQM from enhancing a block of elements?
- How do I control page titles?
- How do I load a page?
- Events
- How do I use touch and mouse events?
- Theme and styling
- How does theming work?
- Apps
- How do I need to configure PhoneGap/Cordova?

# Navbar API

jQuery Mobile has a very basic navbar widget that is useful for providing up to 5 buttons with optional icons in a bar.

## Navbar basics

A navbar is coded as an unordered list of links wrapped in a container element that has the `data-role="navbar"` attribute. When a link in the navbar is clicked it gets the active (selected) state. The `ui-btn-active` class is first removed from all anchors in the navbar before it is added to the activated link. If this is a link to another page, the class will be removed again after the transition has completed.

To set an item to the active state, add `class="ui-btn-active"` to an anchor in the markup. Additionally add a class of `ui-state-persist` to make the framework restore the active state each time the page is shown while it exists in the DOM.

Navbars with 1 item will render as 100% wide.

- One

The navbar items are set to divide the space evenly so in this case, each button is 1/2 the width of the browser window:

- One
- Two

Adding a third item will automatically make each button 1/3 the width of the browser window:

- One
- Two
- Three

Adding a fourth more item will automatically make each button 1/4 the width of the browser window:

- One
- Two
- Three
- Four

The navbar maxes out with 5 items, each 1/5 the width of the browser window:

- One
- Two
- Three
- Four
- Five

## Multi-row

If more than 5 items are added, the navbar will simply wrap to multiple lines of two across:

- One
- Two
- Three
- Four
- Five
- Six
- Seven
- Eight
- Nine
- Ten

## Navbars in headers

If you want to add a navbar to the top of the page, you can still have a page title and buttons. Just add the navbar container inside the header block, right after the title and buttons in the source order.

# I'm a header

Options

- One
- Two
- Three

## Navbars in footers

If you want to add a navbar to the bottom of the page so it acts more like a tab bar, simply wrap the navbar in a container with a `data-role="footer"`

#### I'm the footer

- One
- Two
- Three

## Persistent

The persistent navbar variation is designed to work more like a tab bar that stays fixed as you navigate across pages. To set an item to the active state upon initialization of the navbar, add `class="ui-btn-active"` to the corresponding anchor in your markup. Additionally add a class of `ui-state-persist` to make the framework restore the active state each time the page is shown while it exists in the DOM.

## Icons

Icons can be added to navbar items by adding the `data-icon` attribute specifying a standard mobile icon to each anchor. By default, icons are added above the text (`data-iconpos="top"`). The following examples add icons to a navbar in a footer.

- Summary
- Favs
- Setup

## Icon position

The icon position is set on the navbar container instead of for individual links within for visual consistency. For example, to place the icons below the labels, add the `data-iconpos="bottom"` attribute to the navbar container.

This will result in a bottom icon alignment:

- Summary
- Favs
- Setup

The icon position can be set to `data-iconpos="left"`:

- Summary
- Favs
- Setup

Or the icon position can be set to `data-iconpos="right"`:

- Summary
- Favs
- Setup

## 3rd party icon sets

You can add any of the popular icon libraries like Glyphish to achieve the iOS style tab that has large icons stacked on top of text labels. All that is required is a bit of custom styles to link to the icons and position them in the navbar. Here is an example using Glyphish icons and custom styles (view page source for styles) in our navbar:

Icons by Joseph Wain / glyphish.com. Licensed under the Creative Commons Attribution 3.0 United States License.

## Themes

Navbars inherit the theme swatch from their parent container, just like buttons. If a navbar is placed in the header or footer toolbar, it will inherit the default toolbar swatch "a" for bars unless you set this in the markup.

Here are a few examples of navbars in various container swatches that automatically inherit their parent's swatch letter. Note that in these examples, instead of using a `data-theme` attribute, we're manually adding the swatch classes to apply the body swatch (`ui-body-a`) and the class to add the standard body padding (ui-body), but the inheritance works the same way:

### Swatch "a"

- A
- B
- C
- D
- E

### Swatch "d"

- A
- B
- C
- D
- E

To set the theme color for a navbar item, add the `data-theme` attribute to the individual links and specify a theme swatch. Note that applying a theme swatch to the navbar container is not supported.

- A
- B
- C
- D
- E