### Default panel options

This panel has all the default options: positioned on the left with the reveal display mode. The panel markup is before the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel

#

Navigation Search

- Accordion
- AJAX Navigation
- Autocomplete
- Buttons
- Checkboxes
- Collapsibles
- Controlgroup
- Filterable New
- Dialogs
- Fixed toolbars
- Flip switch, slider
- Flip switch New
- Footer toolbar
- Form elements
- Grids
- Header toolbar
- Icons New
- Links
- Listviews
- Loader
- Navbar
- Navbar, persistent
- Pages
- Panels
- Popup
- Radio buttons
- Select
- Select, custom
- Slider, single
- Slider, dual range
- Table, column toggle
- Table, reflow
- Text inputs & textarea
- Transitions
- Collapsibles
- Dynamic collapsible
- Controlgroups
- Dynamic controlgroup
- Filterable
- Filterable inside custom select
- Listviews
- Grid Listview
- Autodividers Linkbar
- Autodividers Selector
- Maps
- Google Maps & Geolocation
- Google Maps with List toggle
- Navigation
- Backbone and Require.js example
- Redirection with server-side support
- Panels
- Panel styling
- Open panel on swipe
- Popups
- Dynamic popup
- Popup arrow size
- Popup alignment
- Responsive Tables
- Reflow: Custom styles
- Reflow: Heading groups
- Column toggle: Customization options
- Column toggle: Heading groups
- 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?
- How do I turn off the automatic hiding of the url bar?
- 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?

# External Panels API

Flexible by design, panels can be used for navigation, forms, inspectors and more.

## External Panels

The panels below are all located outside the page. Panels outside of a page must be initalized manually and will not be handled by auto init

Panels outside of pages will remain in the dom unless manually removed and can be opened or closed from any page

Navigate to page 2 below to see this behavior. This page doesn't contain panels.

Navigate to page 2

Left panel examples

Overlay Reveal Push

Right panel examples

Overlay Reveal Push

The position of the panel on the screen is set by the `data-position` attribute. The default value of the attribute is `left`, meaning it will appear from the left edge of the screen. Specify `data-position="right"` for it to appear from the right edge instead.

The display mode of the panel is set by the `data-display` attribute. The value of the attribute defaults to `reveal`, meaning the panel will sit under the page and reveal as the page slides away. Specify `data-display="overlay"` for the panel to appear on top of the page contents. A third mode, `data-display="push"` animates both the panel and page at the same time.

## Where panel markup goes in the markup

A panel must be a sibling to the header, content and footer elements inside a jQuery Mobile page. You can add the panel markup either before or after these elements, but not in between. A panel cannot be placed outside a page, but this constraint will be removed in a future version.

Here is an example of the panel before the header, content and footer in the source order:

    <div data-role="page">

    <div data-role="panel" id="mypanel">
        <!-- panel content goes here -->
    </div><!-- /panel -->

    <!-- header -->
    <!-- content -->
    <!-- footer -->

    </div><!-- page -->

Alternatively, it's possible to add the panel markup after the header, content and footer in the source order, just before the end of the page container. Where in the source order you place the panel markup will depend on how you want the page content to read for people experiencing the page on a C-grade device (HTML only) or for a screen reader.

## Dynamic content

When you dynamically add content to a panel or make hidden content visible while the panel is open, you have to trigger the `updatelayout` event on the panel.

    $( "#mypanel" ).trigger( "updatelayout" );

The framework will then check the new height of the panel contents. If it exceeds the screen height, it will set the page `min-height` to this height and unfix panels with `data-position-fixed="true"`. See also Panel positioning.

## Opening a panel

To control a panel from a link, set the `href` to the `ID` of the panel you want to toggle (`mypanel` in the example above). This instructs the framework to bind the link to the panel. This link will toggle the visibility of the panel so tapping it will open the panel, and tapping it again will close it.

Default panel

## Closing a panel

Clicking the link that opened the panel, swiping left or right, or tapping the Esc key will close the panel. To turn off the swipe-to-close behavior, add the `data-swipe-close="false"` attribute to the panel.

By default, panels can also be closed by clicking outside the panel onto the page contents. To prevent this behavior, add the `data-dismissible="false"` attribute to the panel. It's possible to have the panel and page sit side-by-side at wider screen widths and prevent the click-out-to-close behavior only above a certain screen width by applying a media query. See the responsive section below for details.

It's common to also add a close button inside the panel. To add the link that will close the panel, add the `data-rel="close"` attribute to tell the framework to close that panel when clicked. It's important to ensure that this link also makes sense if JavaScript isn't available, so we recommend that the `href` point to the ID of the page to which the user should jump when closing. For example, if the button to open the panel is in the header bar that has and ID of `my-header`, the close link in the panel should be:

    <a href="#my-header" data-rel="close">Close panel</a>

## Panel animations

Panels will animate if the browser supports 3D transforms — the same criteria for CSS animation support we use for page transitions. Panel animations use `translate3d(x,y,z)` CSS transforms to ensure they are hardware accelerated and smooth.

The `animate` option allows you to turn off panel animations for all devices. To turn off animations via markup, add the `data-animate="false"` attribute to the panel container.

## Panel positioning

The panel will be displayed with the `position:absolute` CSS property, meaning it will scroll with the page. When a panel is opened the framework checks to see if the bottom of the panel contents is in view. If not, it scrolls to the top of the page.

You can set a panel to `position:fixed`, so its contents will appear no matter how far down the page you're scrolled, by adding the `data-position-fixed="true"` attribute to the panel. The framework also checks to see if the panel contents will fit within the viewport before applying the fixed positioning because this property would prevent the panel contents from scrolling and make it inaccessible. `overflow` is not well supported enough to use at this time. If the panel contents are too long to fit within the viewport, the framework will simply display the panel without fixed positioning. See an example of panels with fixed positioning.

## Styling panels

By default, panels have very simple styles to let you customize them as needed. Panels are essentially just simple blocks with no margins that sit on either side of the page content. The framework wraps the panel content in a `div` with class `ui-panel-inner` which has a padding of 15 pixels. If needed you can override this with custom CSS or use option `classes.panelInner` to set a different class name for the `div`.

Panels have a fixed width of 17em (272 pixels) which is narrow enough to still show some of the page contents when open to make clicking out to close easy, while still looking good on wider tablet or desktop screens. The styles to set widths on panels are fairly complex but these can be overridden with CSS as needed.

Other than the theme background, width and 100% height styles, panels have very little styling on their own. The default theme for panels is "c". You can set a different theme for the panel by adding a `data-theme` attribute to the panel container, or you can set `data-theme="none"` and add your own classes to style it as needed.

Note that adding padding, borders, or margins directly to the panel container will alter the overall dimensions and could cause the positioning and animation to be affected. To avoid this, apply styles to the panel content wrapper (`.ui-panel-inner`).

## Making the panel responsive

When the push or reveal display is used, a panel pushes the page aside when it opens. Since some of the page is pushed offscreen, the panel is modal and must be closed to interact with the page content again. On larger screens, you may want to have the panel work more like a collapsible column that can be opened and used alongside the page to make better use of the screen real estate.

To make the page work alongside the open panel, it needs to re-flow to a narrower width so it will fit next to the panel. This can be done purely with CSS by adding a left or right margin equal to the panel width (17em) to the page contents to force a re-flow. Second, the invisible layer placed over the page for the click-out-to-dismiss behavior is hidden with CSS so you can click on the page and not close the menu.

Here is an example of these rules wrapped in a media query to only apply this behavior above 35em (560px):

    @media (min-width:35em){

    	/* wrap on wide viewports once open */

    	.ui-page-panel-open .ui-panel-content-fixed-toolbar-display-push.ui-panel-content-fixed-toolbar-position-left,
    	.ui-page-panel-open .ui-panel-content-fixed-toolbar-display-reveal.ui-panel-content-fixed-toolbar-position-left,
    	.ui-page-panel-open .ui-panel-content-wrap-display-push.ui-panel-content-wrap-position-left,
    	.ui-page-panel-open .ui-panel-content-wrap-display-reveal.ui-panel-content-wrap-position-left {
    		margin-right: 17em;
    	}
    	.ui-page-panel-open .ui-panel-content-fixed-toolbar-display-push.ui-panel-content-fixed-toolbar-position-right,
    	.ui-page-panel-open .ui-panel-content-fixed-toolbar-display-reveal.ui-panel-content-fixed-toolbar-position-right,
    	.ui-page-panel-open .ui-panel-content-wrap-display-push.ui-panel-content-wrap-position-right,
    	.ui-page-panel-open .ui-panel-content-wrap-display-reveal.ui-panel-content-wrap-position-right {
    		margin-left: 17em;
    	}
    	.ui-page-panel-open .ui-panel-content-fixed-toolbar-display-push,
    	.ui-page-panel-open .ui-panel-content-fixed-toolbar-display-reveal {
    		width: auto;
    	}

    	/* disable "dismiss" on wide viewports */
    	.ui-panel-dismiss {
    		display: none;
    	}
    	/* same as the above but for panels with display mode "push" only */
    	.ui-panel-dismiss-display-push {
    		display: none;
    	}

    }

#### Applying a preset breakpoint

Included in the widget styles is a breakpoint preset for this behavior that kicks in at 55em (880px). This breakpoint is not applied by default to make it easier for you to write custom breakpoints that work best for your content and design. To apply the breakpoint preset, add the `ui-responsive-panel` class to the page wrapper (not the panel). See an example of a responsive panel page.

### Left Panel: Reveal

This panel is positioned on the left with the reveal display mode. The panel markup is after the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel

### Left Panel: Push

This panel is positioned on the left with the push display mode. The panel markup is after the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel

### Left Panel: Overlay

This panel is positioned on the left with the overlay display mode. The panel markup is after the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel

### Right Panel: Reveal

This panel is positioned on the right with the reveal display mode. The panel markup is after the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel

### Right Panel: Push

This panel is positioned on the right with the push display mode. The panel markup is after the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel

### Right Panel: Overlay

This panel is positioned on the right with the overlay display mode. The panel markup is after the header, content and footer in the source order.

To close, click off the panel, swipe left or right, hit the Esc key, or use the button below:

Close panel