jquery-mobile/docs/api/globalconfig.html

<!DOCTYPE html>
<html class="ui-mobile-rendering">
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<title>jQuery Mobile Docs - Configuring default settings</title>
	<link rel="stylesheet"  href="../../css/themes/default/jquery.mobile.css" />
	<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>

	<script data-main="../../js/jquery.mobile.docs" src="../../external/requirejs/require.js"></script>
	<script src="../../js/jquery.js"></script>
</head>
<body>

<div data-role="page" class="type-interior">

	<div data-role="header" data-theme="f">
		<h1>Configuring Defaults</h1>
		<a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse" class="ui-btn-right jqm-home">Home</a>
	</div><!-- /header -->

	<div data-role="content" data-theme="c">
		<div class="content-primary">

			<h2>Working with jQuery Mobile's Auto-initialization</h2>
			<p>Unlike other jQuery projects, such as jQuery and jQuery UI, jQuery Mobile automatically applies many markup enhancements as soon as it loads (long before <code>document.ready</code> event fires). These enhancements are applied based on jQuery Mobile's default configuration, which is designed to work with common scenarios, but may or may not match your particular needs. Fortunately, these settings are easy to configure.</p>

			<h3>The mobileinit event</h3>
			<p>When the jQuery Mobile starts to execute, it triggers a <code>mobileinit</code> event on the <code>document</code> object, to which you can bind to apply overrides to jQuery Mobile's defaults.</p>

			<pre>
				<code>
$(document).bind("mobileinit", function(){
  //apply overrides here
});
				</code>
			</pre>

			<p>Because the <code>mobileinit</code> event is triggered immediately upon execution, you'll need to bind your event handler before jQuery Mobile is loaded. Thus, we recommend linking to your JavaScript files in the following order:</p>

			<pre>
				<code>
&lt;script src=&quot;jquery.js&quot;&gt;&lt;/script&gt;
<strong>&lt;script src=&quot;custom-scripting.js&quot;&gt;&lt;/script&gt;</strong>
&lt;script src=&quot;jquery-mobile.js&quot;&gt;&lt;/script&gt;
				</code>
			</pre>

			<p>Within this event binding, you can configure defaults either by extending the <code>$.mobile</code> object using jQuery's <code>$.extend</code> method:</p>

			<pre>
				<code>
$(document).bind("mobileinit", function(){
  $.extend(  $.mobile , {
    <strong>foo: bar</strong>
  });
});
				</code>
			</pre>

			<p>...or by setting them individually:</p>
			<pre>
				<code>
$(document).bind("mobileinit", function(){
  <strong>$.mobile.foo = bar;</strong>
});
				</code>
			</pre>

		<p>To quickly preview these global configuration options in action, check out the <a href="../config/index.html">config test pages</a>.</p>

		<h2>Configurable options</h2>
		<p>The following defaults are configurable via the <code>$.mobile</code> object:</p>

<dl>
	<dt><code>ns</code> <em>string</em>, default: ""</dt>
	<dd>The namespace used in data- attributes, for example, data-role. Can be set to anything, including a blank string which is the default. When using, it's clearest if you include a trailing dash, such as "mynamespace-" which maps to <code>data-mynamespace-foo="..."</code>.
		<p><strong>NOTE:</strong> if you're using data- namespacing, you'll need to manually update/override one selector in the theme CSS. The following data selectors should incorporate the namespace you're using:
		<pre><code>
.ui-mobile [data-<strong>mynamespace-</strong>role=page], .ui-mobile [data-<strong>mynamespace-</strong>role=dialog], .ui-page { ...
		</code></pre>
		</p>
	</dd>

	<dt><code>autoInitializePage</code> <em>boolean</em>, default: true</dt>
	<dd>When the DOM is ready, the framework should automatically call <code>$.mobile.initializePage</code>. If false, page will not initialize, and will be visually hidden until <code>$.mobile.initializePage</code> is manually called.</dd>

	<dt><code>subPageUrlKey</code> <em>string</em>, default: "ui-page"</dt>
	<dd>The url parameter used for referencing widget-generated sub-pages (such as those generated by nested listviews). Translates to to <em>example.html<strong>&ui-page=</strong>subpageIdentifier</em>. The hash segment before &ui-page= is used by the framework for making an Ajax request to the URL where the sub-page exists.</dd>

	<dt><code>activePageClass</code> <em>string</em>, default: "ui-page-active"</dt>
	<dd>The class assigned to page currently in view, and during transitions</dd>


	<dt><code>activeBtnClass</code> <em>string</em>, default: "ui-btn-active"</dt>
	<dd>The class used for "active" button state, from CSS framework.</dd>

	<dt><code>ajaxEnabled</code> <em>boolean</em>, default: true</dt>
	<dd>jQuery Mobile will automatically handle link clicks and form submissions through Ajax, when possible. If false, url hash listening will be disabled as well, and urls will load as regular http requests.</dd>

	<dt><code>linkBindingEnabled</code> <em>boolean</em>, default: true</dt>
	<dd>jQuery Mobile will automatically bind the clicks on anchor tags in your document. Setting this options to false will prevent all anchor click handling <em>including</em> the addition of active button state and alternate link bluring. This should only be used when attempting to delegate the click management to another library or custom code.</dd>

	<dt><code>hashListeningEnabled</code> <em>boolean</em>, default: true</dt>
	<dd>jQuery Mobile will automatically listen and handle changes to the location.hash. Disabling this will prevent jQuery Mobile from handling hash changes, which allows you to handle them yourself, or simply to use simple deep-links within a document that scroll to a particular ID.</dd>

	<dt><code>pushStateEnabled</code> <em>boolean</em>, default: true</dt>
	<dd>Enhancement to use <code>history.replaceState</code> in supported browsers, to convert the hash-based Ajax URL into the full document path. Note that we <a href="../pages/page-navmodel.html">recommend</a> disabling this feature if Ajax is disabled or if extensive use of external links are used.</dd>

	<dt><code>defaultPageTransition</code> <em>string</em>, default: 'slide'</dt>
	<dd>Set the default transition for page changes that use Ajax. Set to 'none' for no transitions by default.</dd>

	<dt><code>touchOverflowEnabled</code> <em>boolean</em>, default: false</dt>
	<dd>Enable smoother page transitions and true fixed toolbars in devices that support both the <code>overflow:</code> and <code>overflow-scrolling: touch; </code> CSS properties.</dd>

	<dt><code>defaultDialogTransition</code> <em>string</em>, default: 'pop'</dt>
	<dd>Set the default transition for dialog changes that use Ajax. Set to 'none' for no transitions by default.</dd>

	<dt><code>minScrollBack</code> <em>string</em>, default: 250</dt>
	<dd>Minimum scroll distance that will be remembered when returning to a page. </dd>

	<dt><code>loadingMessage</code> <em>string</em>, default: "loading"</dt>
	<dd>Set the text that appears when a page is loading. If set to false, the message will not appear at all.</dd>
	
	<dt><code>loadingMessageTheme</code> <em>string</em>, default: "a"</dt>
	<dd>Set the theme that the loading message box uses, when text is visible.</dd>

	<dt><code>pageLoadErrorMessage</code> <em>string</em>, default: "Error Loading Page"</dt>
	<dd>Set the text that appears when a page fails to load through Ajax.</dd>
	
	<dt><code>pageLoadErrorMessageTheme</code> <em>string</em>, default: "e"</dt>
	<dd>Set the theme that the error message box uses.</dd>
	
	<dt><code>loadingMessageTextVisible</code> <em>string</em>, default: false</dt>
	<dd>Should the text be visible when loading message is shown. (note: currently, the text is always visible for loading errors)</dd>
	
	
	<dt><code>gradeA</code> <em>function that returns a boolean</em>, default: a function returning the value of $.support.mediaquery</dt>
	<dd>Any support conditions that must be met in order to proceed.</dd>


</dl>
	</div><!--/content-secondary -->

	<div class="content-secondary">

		<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">

				<h3>More in this section</h3>

				<ul data-role="listview"  data-theme="c" data-dividertheme="d">

					<li data-role="list-divider">API</li>
					<li data-theme="a"><a href="../../docs/api/globalconfig.html">Configuring defaults</a></li>
					<li><a href="../../docs/api/events.html">Events</a></li>
					<li><a href="../../docs/api/methods.html">Methods &amp; Utilities</a></li>
					<li><a href="../../docs/api/data-attributes.html">Data attribute reference</a></li>
					<li><a href="../../docs/api/themes.html">Theme framework</a></li>
				</ul>
		</div>
	</div>

</div><!-- /content -->

<div data-role="footer" class="footer-docs" data-theme="c">
		<p>&copy; 2011 The jQuery Project</p>
</div>

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

</body>
</html>
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`<!DOCTYPE html>`
add ui-mobile-rendering to docs to temprarily prevent fouc with async load. @gseguin to address with jqm-docs.js change 2012-01-04 21:59:17 +00:00			`<html class="ui-mobile-rendering">`
docs updates 2010-11-11 18:32:46 +00:00			`<head>`
Added viewport meta elements to the markup of every template and removed the metaViewportContent option from code and docs. IE does not support generated viewport tags. 2011-02-18 20:00:18 +00:00			`<meta charset="utf-8">`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`<meta name="viewport" content="width=device-width, initial-scale=1">`
			`<title>jQuery Mobile Docs - Configuring default settings</title>`
Updated docs’ CSS to use new @import scheme. 2012-01-10 21:35:08 +00:00			`<link rel="stylesheet" href="../../css/themes/default/jquery.mobile.css" />`
added demo css file to api folder pages 2010-11-11 21:15:13 +00:00			`<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>`
Move require.js to first tag so it can catch jquery module registration Otherwise jquery may be loaded twice 2012-01-13 05:25:59 +00:00
Added require.js 1.0.3 as a submodule 2011-12-24 08:48:08 +00:00			`<script data-main="../../js/jquery.mobile.docs" src="../../external/requirejs/require.js"></script>`
Move require.js to first tag so it can catch jquery module registration Otherwise jquery may be loaded twice 2012-01-13 05:25:59 +00:00			`<script src="../../js/jquery.js"></script>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`</head>`
			`<body>`
docs updates 2010-11-11 18:32:46 +00:00
reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00			`<div data-role="page" class="type-interior">`
docs updates 2010-11-11 18:32:46 +00:00
more docs updates. moved to the green header, set default transition dynamically 2011-06-20 19:17:05 +00:00			`<div data-role="header" data-theme="f">`
Content cleanup 2010-11-11 19:38:13 +00:00			`<h1>Configuring Defaults</h1>`
changed the default namespace to "" and updated the docs/demos as such 2011-03-10 03:36:14 +00:00			`<a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse" class="ui-btn-right jqm-home">Home</a>`
docs updates 2010-11-11 18:32:46 +00:00			`</div><!-- /header -->`

changed the default namespace to "" and updated the docs/demos as such 2011-03-10 03:36:14 +00:00			`<div data-role="content" data-theme="c">`
reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00			`<div class="content-primary">`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`<h2>Working with jQuery Mobile's Auto-initialization</h2>`
Update docs/api/globalconfig.html 2011-11-26 22:14:26 +00:00			`<p>Unlike other jQuery projects, such as jQuery and jQuery UI, jQuery Mobile automatically applies many markup enhancements as soon as it loads (long before <code>document.ready</code> event fires). These enhancements are applied based on jQuery Mobile's default configuration, which is designed to work with common scenarios, but may or may not match your particular needs. Fortunately, these settings are easy to configure.</p>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`<h3>The mobileinit event</h3>`
			`<p>When the jQuery Mobile starts to execute, it triggers a <code>mobileinit</code> event on the <code>document</code> object, to which you can bind to apply overrides to jQuery Mobile's defaults.</p>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`<pre>`
			`<code>`
			`$(document).bind("mobileinit", function(){`
			`//apply overrides here`
			`});`
			`</code>`
			`</pre>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`<p>Because the <code>mobileinit</code> event is triggered immediately upon execution, you'll need to bind your event handler before jQuery Mobile is loaded. Thus, we recommend linking to your JavaScript files in the following order:</p>`

			`<pre>`
			`<code>`
			`<script src="jquery.js"></script>`
			`<strong><script src="custom-scripting.js"></script></strong>`
			`<script src="jquery-mobile.js"></script>`
			`</code>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`</pre>`

docs updates 2010-11-11 18:32:46 +00:00			`<p>Within this event binding, you can configure defaults either by extending the <code>$.mobile</code> object using jQuery's <code>$.extend</code> method:</p>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`<pre>`
			`<code>`
			`$(document).bind("mobileinit", function(){`
			`$.extend( $.mobile , {`
			`<strong>foo: bar</strong>`
			`});`
			`});`
			`</code>`
			`</pre>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`<p>...or by setting them individually:</p>`
			`<pre>`
			`<code>`
changed docs for live event => bind event 2010-11-12 20:46:00 +00:00			`$(document).bind("mobileinit", function(){`
docs updates 2010-11-11 18:32:46 +00:00			`<strong>$.mobile.foo = bar;</strong>`
			`});`
			`</code>`
			`</pre>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
Added config test page for jQuery core 1.8B1 2011-10-13 19:46:55 +00:00			`<p>To quickly preview these global configuration options in action, check out the <a href="../config/index.html">config test pages</a>.</p>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<h2>Configurable options</h2>`
			`<p>The following defaults are configurable via the <code>$.mobile</code> object:</p>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<dl>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`<dt><code>ns</code> <em>string</em>, default: ""</dt>`
documented theme css namespace caveat. Fixes #1341 2011-04-01 18:58:36 +00:00			`<dd>The namespace used in data- attributes, for example, data-role. Can be set to anything, including a blank string which is the default. When using, it's clearest if you include a trailing dash, such as "mynamespace-" which maps to <code>data-mynamespace-foo="..."</code>.`
			`<p><strong>NOTE:</strong> if you're using data- namespacing, you'll need to manually update/override one selector in the theme CSS. The following data selectors should incorporate the namespace you're using:`
			`<pre><code>`
			`.ui-mobile [data-<strong>mynamespace-</strong>role=page], .ui-mobile [data-<strong>mynamespace-</strong>role=dialog], .ui-page { ...`
			`</code></pre>`
			`</p>`
			`</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>autoInitializePage</code> <em>boolean</em>, default: true</dt>`
typo: until is written twice 2011-11-30 21:54:57 +00:00			`<dd>When the DOM is ready, the framework should automatically call <code>$.mobile.initializePage</code>. If false, page will not initialize, and will be visually hidden until <code>$.mobile.initializePage</code> is manually called.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
Updated markup to match the new API styles 2011-07-28 20:41:02 +00:00			`<dt><code>subPageUrlKey</code> <em>string</em>, default: "ui-page"</dt>`
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<dd>The url parameter used for referencing widget-generated sub-pages (such as those generated by nested listviews). Translates to to <em>example.html<strong>&ui-page=</strong>subpageIdentifier</em>. The hash segment before &ui-page= is used by the framework for making an Ajax request to the URL where the sub-page exists.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>activePageClass</code> <em>string</em>, default: "ui-page-active"</dt>`
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<dd>The class assigned to page currently in view, and during transitions</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00

			`<dt><code>activeBtnClass</code> <em>string</em>, default: "ui-btn-active"</dt>`
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<dd>The class used for "active" button state, from CSS framework.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>ajaxEnabled</code> <em>boolean</em>, default: true</dt>`
added ajaxEnabled option. ajaxLinksEnabled and ajaxFormsEnabled are deprecated and will be removed by 1.0. Fixes #851 2011-01-24 00:03:35 +00:00			`<dd>jQuery Mobile will automatically handle link clicks and form submissions through Ajax, when possible. If false, url hash listening will be disabled as well, and urls will load as regular http requests.</dd>`
Added global config option "useFastClick", so that the changes we made for automated ajax handling since A4 can be disabled if needed, for whatever reason. When handling clicks and taps automatically with Ajax, this option will use jQuery Mobile's <code>vclick</code> event, enabling page changes to happen slightly sooner on devices that support touch events, and keeping the address bar hidden during page transtions. When disabled, the automatied Ajax handling will use an ordinary <code>click</code> event instead. This option has no effect on non-touch devices, but when enabled, it may interfere with jQuery plugins that bind to click events rather than vclick events. Fixes #1857 2011-06-20 15:35:09 +00:00
linkBindingEnabled docs 2011-10-20 22:30:29 +00:00			`<dt><code>linkBindingEnabled</code> <em>boolean</em>, default: true</dt>`
			`<dd>jQuery Mobile will automatically bind the clicks on anchor tags in your document. Setting this options to false will prevent all anchor click handling <em>including</em> the addition of active button state and alternate link bluring. This should only be used when attempting to delegate the click management to another library or custom code.</dd>`

whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`<dt><code>hashListeningEnabled</code> <em>boolean</em>, default: true</dt>`
documented hashListeningEnabled. Fixes #1091 2011-03-31 03:28:53 +00:00			`<dd>jQuery Mobile will automatically listen and handle changes to the location.hash. Disabling this will prevent jQuery Mobile from handling hash changes, which allows you to handle them yourself, or simply to use simple deep-links within a document that scroll to a particular ID.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>pushStateEnabled</code> <em>boolean</em>, default: true</dt>`
Updated docs to clarify the replaceState known issues and to add docs on the pushStateEnabled option 2011-10-10 17:14:59 +00:00			`<dd>Enhancement to use <code>history.replaceState</code> in supported browsers, to convert the hash-based Ajax URL into the full document path. Note that we <a href="../pages/page-navmodel.html">recommend</a> disabling this feature if Ajax is disabled or if extensive use of external links are used.</dd>`
Combined settings and global config pages 2010-11-11 19:25:41 +00:00
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`<dt><code>defaultPageTransition</code> <em>string</em>, default: 'slide'</dt>`
- Externalize some of the nested functions in changePage(). - Modified changePage() so that it can take an options object. Updated all references throughout the framework. - Split $.mobile.pageLoading() into 2 functions $.mobile.show/hidePageLoadingMsg(). Updated docs accordingly. - Renamed $.mobile.defaultTransition to $.mobie.defaultPageTransition. Updated docs accordingly. - Added $.mobile.defaultDialogTransition so that it isn't hard coded in the changePage/transitionPages and select code. - Hand integrated jquery.mobile.navigation.js checkins from master: 4b4ee54a, e775f5e8, e597ccb3, 084bbbd8. 2011-05-16 23:02:26 +00:00			`<dd>Set the default transition for page changes that use Ajax. Set to 'none' for no transitions by default.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>touchOverflowEnabled</code> <em>boolean</em>, default: false</dt>`
Updated docs to clarify the replaceState known issues and to add docs on the pushStateEnabled option 2011-10-10 17:14:59 +00:00			`<dd>Enable smoother page transitions and true fixed toolbars in devices that support both the <code>overflow:</code> and <code>overflow-scrolling: touch; </code> CSS properties.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>defaultDialogTransition</code> <em>string</em>, default: 'pop'</dt>`
- Externalize some of the nested functions in changePage(). - Modified changePage() so that it can take an options object. Updated all references throughout the framework. - Split $.mobile.pageLoading() into 2 functions $.mobile.show/hidePageLoadingMsg(). Updated docs accordingly. - Renamed $.mobile.defaultTransition to $.mobie.defaultPageTransition. Updated docs accordingly. - Added $.mobile.defaultDialogTransition so that it isn't hard coded in the changePage/transitionPages and select code. - Hand integrated jquery.mobile.navigation.js checkins from master: 4b4ee54a, e775f5e8, e597ccb3, 084bbbd8. 2011-05-16 23:02:26 +00:00			`<dd>Set the default transition for dialog changes that use Ajax. Set to 'none' for no transitions by default.</dd>`
added minScrollBack feature to core options. This is the minimum scroll distance that will be jumped-to when returning to a page. By default, the distance is screen.height /2. If you really needed to disable scroll memory altogether, this could be set to Infinity. Note that disabling scroll memory altogether is almost never a good idea for usability, but the option is there. 2011-06-17 20:33:19 +00:00
Update docs/api/globalconfig.html 2011-12-14 17:53:17 +00:00			`<dt><code>minScrollBack</code> <em>string</em>, default: 250</dt>`
added minScrollBack feature to core options. This is the minimum scroll distance that will be jumped-to when returning to a page. By default, the distance is screen.height /2. If you really needed to disable scroll memory altogether, this could be set to Infinity. Note that disabling scroll memory altogether is almost never a good idea for usability, but the option is there. 2011-06-17 20:33:19 +00:00			`<dd>Minimum scroll distance that will be remembered when returning to a page. </dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>loadingMessage</code> <em>string</em>, default: "loading"</dt>`
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<dd>Set the text that appears when a page is loading. If set to false, the message will not appear at all.</dd>`
Added an optional 1.0-style loading box design, configurable via a new loadingMessageTextVisible option, which defaults to false for regular loading messages, but is true for internal error messages. In order to support this change, the show loader method was modified with 3 arguments: theme, text, and text-only. Other new core options have been added to configure the theme for default and error message boxes: loadingMessageTheme and pageLoadErrorMessageTheme. 2012-01-27 11:42:22 +00:00
			`<dt><code>loadingMessageTheme</code> <em>string</em>, default: "a"</dt>`
			`<dd>Set the theme that the loading message box uses, when text is visible.</dd>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
			`<dt><code>pageLoadErrorMessage</code> <em>string</em>, default: "Error Loading Page"</dt>`
Added pageLoadErrorMessage option. Defaults to "Error Loading Page". Documentation included. Fixes #1258 and Fixes #363 2011-03-27 15:45:03 +00:00			`<dd>Set the text that appears when a page fails to load through Ajax.</dd>`
Added an optional 1.0-style loading box design, configurable via a new loadingMessageTextVisible option, which defaults to false for regular loading messages, but is true for internal error messages. In order to support this change, the show loader method was modified with 3 arguments: theme, text, and text-only. Other new core options have been added to configure the theme for default and error message boxes: loadingMessageTheme and pageLoadErrorMessageTheme. 2012-01-27 11:42:22 +00:00
			`<dt><code>pageLoadErrorMessageTheme</code> <em>string</em>, default: "e"</dt>`
			`<dd>Set the theme that the error message box uses.</dd>`

			`<dt><code>loadingMessageTextVisible</code> <em>string</em>, default: false</dt>`
			`<dd>Should the text be visible when loading message is shown. (note: currently, the text is always visible for loading errors)</dd>`


Combined settings and global config pages 2010-11-11 19:25:41 +00:00
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`<dt><code>gradeA</code> <em>function that returns a boolean</em>, default: a function returning the value of $.support.mediaquery</dt>`
Combined settings and global config pages 2010-11-11 19:25:41 +00:00			`<dd>Any support conditions that must be met in order to proceed.</dd>`


			`</dl>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`</div><!--/content-secondary -->`

reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00			`<div class="content-secondary">`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
adjusted the presentation of the left nav and footer for the docs 2011-09-29 20:35:31 +00:00			`<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
more updates to the docs markup. getting close! 2011-06-20 22:23:09 +00:00			`<h3>More in this section</h3>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
more docs updates. moved to the green header, set default transition dynamically 2011-06-20 19:17:05 +00:00			`<ul data-role="listview" data-theme="c" data-dividertheme="d">`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00			`<li data-role="list-divider">API</li>`
			`<li data-theme="a"><a href="../../docs/api/globalconfig.html">Configuring defaults</a></li>`
			`<li><a href="../../docs/api/events.html">Events</a></li>`
			`<li><a href="../../docs/api/methods.html">Methods & Utilities</a></li>`
Added a data tribute reference page, linked it up 2011-11-04 02:56:54 +00:00			`<li><a href="../../docs/api/data-attributes.html">Data attribute reference</a></li>`
reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00			`<li><a href="../../docs/api/themes.html">Theme framework</a></li>`
			`</ul>`
			`</div>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`</div>`
reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00
			`</div><!-- /content -->`

			`<div data-role="footer" class="footer-docs" data-theme="c">`
updated the footers in the new docs templates 2011-06-20 22:50:52 +00:00			`<p>© 2011 The jQuery Project</p>`
reworked the docs to better accommodate wide screens using a simple responsive layout. Tweaks forthcoming! 2011-06-20 01:58:12 +00:00			`</div>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00
docs updates 2010-11-11 18:32:46 +00:00			`</div><!-- /page -->`

			`</body>`
whitepsace in globalconfig docs 2011-10-20 22:30:04 +00:00			`</html>`