Manages a collection of pages. Smooth Navigation Between Pages Note: The pagecontainer widget is designed to be a singleton instantiated by the framework on the body element. This limitation will be removed in future versions of jQuery Mobile. jQuery Mobile's central abstraction is the use of multiple pages inside a single HTML document. The children of the body are all div elements that have been enhanced into page widgets. These are jQuery M

Triggered on the page being initialized, after initialization occurs. We recommend binding to this event instead of DOM ready() because this will work regardless of whether the page is loaded directly or if the content is pulled into another page as part of the Ajax navigation system. $( document ).on( "pageinit", "#aboutPage", function( event ) { alert( "This page was just enhanced by jQuery Mobile!" ); }); Note: This event has been depreca

Triggers when a scroll finishes. jQuery( ".selector" ).on( "scrollstop", function( event ) { ... } )

Primary unit of content. Pages The page widget is responsible for managing a single item in jQuery Mobile's page-based architecture. It is designed to support either single page widgets within a HTML document, or multiple local internal linked page widgets within a HTML document. The goal of this model is to allow developers to create websites using best practices â where ordinary links will "just work" without any special configuration â while

Triggered when the page has been created in the DOM (via ajax or other) and after all widgets have had an opportunity to enhance the contained markup. Note:This event is part of the page widget as of jQuery Mobile 1.4.0. Please consult the documentation for the page widget's implementation. jQuery( ".selector" ).on( "pagecreate", function( event ) { ... } )

Triggered when the changePage() request fails to load the page. Note: The triggering of this event is deprecated as of jQuery Mobile 1.4.0. It will no longer be triggered in 1.6.0. The replacement for pagechangefailed is the pagecontainer widget's pagecontainerchangefailed event. In jQuery Mobile 1.4.0, the two events are identical except for their name and the fact that pagecontainerchangefailed is triggered on the pagecontainer, whereas page

Triggered on the "fromPage" after the transition animation has completed. Note: The triggering of this event is deprecated as of jQuery Mobile 1.4.0. It will no longer be triggered in 1.6.0. The replacement for pagehide is the pagecontainer widget's pagecontainerhide event. In jQuery Mobile 1.4.0, the two events are identical except for their name and the fact that pagecontainerhide is triggered on the pagecontainer, whereas pagehide is trigge

Event indicating that jQuery Mobile has finished loading. This event is triggered after jQuery Mobile has finished loading, but before it has started enhancing the start page. Thus, handlers of this event have the opportunity to modify jQuery Mobile's global configuration options and all the widgets' default option values before they influence the library's behavior. You must connect a handler to the mobileinit event before you load jQuery Mobi

This event is triggered after the changePage() request has finished loading the page into the DOM and all page transition animations have completed. Note that any pageshow or pagehide events will have fired *BEFORE* this event is triggered. Callbacks for this particular event will be passed a data object as the 2nd arg. The properties for this object are as follows: toPage (object or string) This property represents the page the caller wishes

Triggered before any load request is made. Note: The triggering of this event is deprecated as of jQuery Mobile 1.4.0. It will no longer be triggered in 1.6.0. The replacement for pagebeforeload is the pagecontainer widget's pagecontainerbeforeload event. In jQuery Mobile 1.4.0, the two events are identical except for their name and the fact that pagecontainerbeforeload is triggered on the pagecontainer, whereas pagebeforeload is triggered on