a few more non-namespaced attrs to bring over

Author: scottjehl

docs/_assets/js/_viewsource.js

@@ -21,7 +21,7 @@ $.fn.addSourceLink = function(style){
 			})
 			.click(function(){
 				var codeblock = $('<pre><code></code></pre>');
-				src = src.replace(/&/gmi, '&amp;').replace(/"/gmi, '&quot;').replace(/>/gmi, '&gt;').replace(/</gmi, '&lt;').replace('data-jqm-source="true"','');
+				src = src.replace(/&/gmi, '&amp;').replace(/"/gmi, '&quot;').replace(/>/gmi, '&gt;').replace(/</gmi, '&lt;').replace('data-jq-source="true"','');
 				codeblock.find('code').append(src);
 
 				var activePage = $(this).parents('.ui-page-active');
@@ -38,5 +38,5 @@ $.fn.addSourceLink = function(style){
 
 //set up view source links
 $('div').live('pagebeforecreate',function(){
-	$(this).find('[data-jqm-source="true"]').addSourceLink();
+	$(this).find('[data-jq-source="true"]').addSourceLink();
 });

docs/buttons/buttons-grouped.html

@@ -36,7 +36,7 @@ <h1>Grouped buttons</h1>
 			<a href="index.html" data-jq-role="button">Maybe</a>
 		</div>
 
-		<p>By adding the <code>data-type="horizontal"</code> attribute to the <code>controlgroup</code> container, you can swap to a horizontal-style group that floats the buttons side-by-side and sets the width to only be large enough to fit the content. (Be aware that these will wrap to multiple lines if the number of buttons or the overall text length is too wide for the screen.)
+		<p>By adding the <code>data-jq-type="horizontal"</code> attribute to the <code>controlgroup</code> container, you can swap to a horizontal-style group that floats the buttons side-by-side and sets the width to only be large enough to fit the content. (Be aware that these will wrap to multiple lines if the number of buttons or the overall text length is too wide for the screen.)
 
 		<p>Horizontal grouped buttons:</p>
 		<div data-jq-role="controlgroup" data-jq-type="horizontal">

docs/content/content-collapsible.html

@@ -42,10 +42,10 @@ <h3>I'm a header</h3>
 			</div>
 
 
-		<p>As the example notes, by default the content will be expanded. To collapse the content when the page loads, add the <code>data-collapsed="true"</code> attribute to the wrapper.</p>
+		<p>As the example notes, by default the content will be expanded. To collapse the content when the page loads, add the <code>data-jq-collapsed="true"</code> attribute to the wrapper.</p>
 
 	<code>		
-	&lt;div data-jq-role=&quot;collapsible&quot; <strong>data-collapsed=&quot;true&quot;&gt;</strong>
+	&lt;div data-jq-role=&quot;collapsible&quot; <strong>data-jq-collapsed=&quot;true&quot;&gt;</strong>
 	</code>
 
 		<p>This code will create a collapsible widget like this:</p>
@@ -63,13 +63,13 @@ <h2>Collapsible example</h2>
 
 		<div data-jq-role="collapsible" data-jq-collapsed="true">
 			<h3>Section 1: Collapsed text block</h3>
-			<p>I'm closed when the page loads because I have the <code>data-collapsed="true"</code> attribute on my container. </p>
+			<p>I'm closed when the page loads because I have the <code>data-jq-collapsed="true"</code> attribute on my container. </p>
 			<p>I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. </p>
 		</div><!-- /section 1 -->
 
 		<div data-jq-role="collapsible">
 			<h3>Section 2: Expanded on load</h3>
-			<p>I'm open when the page loads because I don't have the <code>data-collapsed="true"</code> attribute on my container. </p>
+			<p>I'm open when the page loads because I don't have the <code>data-jq-collapsed="true"</code> attribute on my container. </p>
 			<p>I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content. I'm the collapsible content.</p>
 		</div><!-- /section 2 -->
 

docs/forms/docs-forms.html

@@ -58,7 +58,7 @@ <h2>Preventing auto-initialization of form elements</h2>
 });
 		</pre></code>
 
-<p>One special case is that of selects. The above sample will prevent any and all augmentation from taking place on select elements in the page if <code>select</code> is included. If you wish to retain the native performance, look/feel of the menu itself and benefit from the visual augmentation of the select button by jQuery Mobile you can set $.mobile.nativeSelectMenu to true in a <code>mobileinit</code> callback as a global setting or use <code>data-native="true"</code> on a case by case basis.</p>
+<p>One special case is that of selects. The above sample will prevent any and all augmentation from taking place on select elements in the page if <code>select</code> is included. If you wish to retain the native performance, look/feel of the menu itself and benefit from the visual augmentation of the select button by jQuery Mobile you can set $.mobile.nativeSelectMenu to true in a <code>mobileinit</code> callback as a global setting or use <code>data-jq-native="true"</code> on a case by case basis.</p>
 
 			<h2>Dynamic form layout</h2>
 

docs/forms/forms-radiobuttons.html

@@ -78,7 +78,7 @@ <h2>Horizontal radio button sets</h2>
 			<p>Radio buttons can also be used for grouped button sets only a single button can be selected at once, such as a view switcher control. To make a horizontal radio button set, add the <code> data-jq-type="horizontal"</code> to the <code>fieldset</code>.</p>
 
 	<code>
-	&lt;fieldset data-jq-role=&quot;controlgroup&quot; <strong>data-type=&quot;horizontal&quot;</strong> data-jq-role=&quot;fieldcontain&quot;&gt;
+	&lt;fieldset data-jq-role=&quot;controlgroup&quot; <strong>data-jq-type=&quot;horizontal&quot;</strong> data-jq-role=&quot;fieldcontain&quot;&gt;
 	</code>
 
 				<p>The framework will float the labels so they sit side-by-side on a line, hide the radio button icons and only round the left and right edges of the group.</p>

docs/forms/forms-selects.html

@@ -118,7 +118,7 @@ <h2>Select menus</h2>
 
 					<h2>Option to use native menus</h2>
 					<p>The custom select menus add the ability to theme the select and provide visual consistency across platforms In addition, it fixes over some missing functionality on certain platforms: <code>optgroup</code> support on Android, multi-select capability on WebOS, and adds an elegant way to handle placeholder values (explained below).</p>
-					<p>However, there is overhead involved in parsing the native select to build a custom menu and if the number of selects or options within are fairly large, this can impact the performance of the page. By adding the <code>data-native-menu="true"</code> attribute to the <code>select</code>, the framework will use the browser's native select menu when the select button is clicked. Because this option doesn't use any of the custom menu parsing and menu generation logic, it is significantly faster than the custom menu version.</p>
+					<p>However, there is overhead involved in parsing the native select to build a custom menu and if the number of selects or options within are fairly large, this can impact the performance of the page. By adding the <code>data-jq-native-menu="true"</code> attribute to the <code>select</code>, the framework will use the browser's native select menu when the select button is clicked. Because this option doesn't use any of the custom menu parsing and menu generation logic, it is significantly faster than the custom menu version.</p>
 
 			<p>You can also programmatically set the select menu's configuration option to true in a callback bound to the <code>mobileinit</code> event to achieve the same effect. The following must be included in the page after jQuery is loaded but before jQuery Mobile is loaded.</p>
 
@@ -191,7 +191,7 @@ <h2>Placeholder options</h2>
 	<ul>
 		<li>An option with no value attribute (or an empty value attribute)</li>
 		<li>An option with no text node</li>
-		<li>An option with a <code>data-placeholder="true"</code> attribute. (This allows you to use an option that has a value and a textnode as a placeholder option).</li>
+		<li>An option with a <code>data-jq-placeholder="true"</code> attribute. (This allows you to use an option that has a value and a textnode as a placeholder option).</li>
 	</ul>
 
 	<p>You can disable this feature through the selectmenu plugin's <code>hidePlaceholderMenuItems</code> option, like this:</p>

docs/lists/lists-themes.html

@@ -74,7 +74,7 @@ <h2>Theming dividers</h2>
 
 		<h2>Theming count bubbles</h2>
 
-		<p>The theme for <strong>count bubbles</strong> can be set by adding the <code>data-counttheme</code> to the list and specifying a swatch letter. Here is an example with swatch &quot;e&quot; set on the dividers.</p>
+		<p>The theme for <strong>count bubbles</strong> can be set by adding the <code>data-jq-counttheme</code> to the list and specifying a swatch letter. Here is an example with swatch &quot;e&quot; set on the dividers.</p>
 
 <code>
 &lt;ul data-jq-role=&quot;listview&quot; data-jq-inset=&quot;true&quot; data-jq-theme=&quot;a&quot; data-jq-dividertheme=&quot;d&quot; data-jq-counttheme=&quot;e&quot;&gt;
@@ -126,7 +126,7 @@ <h3><a href="index.html">Warning</a></h3>
 <code>
 &lt;ul data-jq-role=&quot;listview&quot; data-jq-inset=&quot;true&quot; data-jq-splittheme=&quot;a&quot;&gt;
 </code>
-		<p>To specify the color swatch for the icon button on the right, add the <code>data-splittheme</code> to the list and specify a swatch letter. This attribute can also be added to individual split inside list items by adding a <code> data-jq-theme</code> attribute to specific links  (see second list item).</p>
+		<p>To specify the color swatch for the icon button on the right, add the <code>data-jq-splittheme</code> to the list and specify a swatch letter. This attribute can also be added to individual split inside list items by adding a <code> data-jq-theme</code> attribute to specific links  (see second list item).</p>
 		<ul data-jq-role="listview" data-jq-inset="true" data-jq-splittheme="a">
 			<li>
 				<img src="images/album-bb.jpg" />
@@ -142,7 +142,7 @@ <h3><a href="index.html">Warning</a></h3>
 			</li>
 		</ul>
 
-		<p>The icon for the split theme can set at the list level by adding the <code>data-spliticon</code> to the list and specifying a <a href="../buttons/buttons-icons.html">standard icon</a>. This attribute can also be added to individual split inside list items by adding a <code> data-jq-icon</code> attribute to specific links (see second list item).</p>
+		<p>The icon for the split theme can set at the list level by adding the <code>data-jq-spliticon</code> to the list and specifying a <a href="../buttons/buttons-icons.html">standard icon</a>. This attribute can also be added to individual split inside list items by adding a <code> data-jq-icon</code> attribute to specific links (see second list item).</p>
 
 <code>
 &lt;ul data-jq-role=&quot;listview&quot; data-jq-inset=&quot;true&quot; data-jq-splittheme=&quot;a&quot; data-jq-spliticon=&quot;plus&quot;&gt;

docs/pages/docs-link-scenarios.html

@@ -28,7 +28,7 @@ <h1>Linking pages</h1>
 				<li><a href="#somelocalID">[href="#somelocalID"]</a></li>
 				<li>Note: an full URL to the same-domain will also work</li>
 				<li data-jq-role="list-divider">Examples of links that trigger a refresh</li>
-				<li><a href="docs/pages/index.html" data-jq-ajax="false">[data-ajax="false"]</a></li>
+				<li><a href="docs/pages/index.html" data-jq-ajax="false">[data-jq-ajax="false"]</a></li>
 				<li><a href="docs/pages/index.html" rel="external">[rel="external"]</a></li>
 				<li><a href="docs/pages/index.html" target="_blank">[target="_blank"]</a></li>
 				<li><a href="mailto:john@doe.com">[href="mailto:john@doe.com"]</a></li>

docs/pages/docs-navmodel.html

@@ -23,7 +23,7 @@ <h2>jQuery Mobile's navigation model</h2>
 
 			<p>A "page" in jQuery Mobile consists of an element (usually a <code>div</code>) with a <code> data-jq-role</code> attribute set to <code>"page"</code>, which generally contains <code>div</code> elements with roles of <code>"header"</code>, <code>"content"</code>, and <code>"footer"</code>, each containing common markup, forms, and custom jQuery Mobile widgets.</p> 
 
-			<p>The basic workflow with page loading is as follows: first, a page is requested with a normal HTTP request, and subsequent "pages" are then requested and injected into that page's DOM. Because of this, the DOM may have a number of "pages" in it at a time, each of which can be re-visited by linking to its <code>data-url</code> attribute.</p> 
+			<p>The basic workflow with page loading is as follows: first, a page is requested with a normal HTTP request, and subsequent "pages" are then requested and injected into that page's DOM. Because of this, the DOM may have a number of "pages" in it at a time, each of which can be re-visited by linking to its <code>data-jq-url</code> attribute.</p> 
 
 			<p>When a url is initially requested, there may be one or more "pages" in the response, and only the first one will be shown. The advantage of storing more than one "page" is that it allows you to pre-fetch static pages that are likely to be visited.</p> 
 
@@ -61,7 +61,7 @@ <h2>Auto-generated pages and sub-hash urls</h2>
 			<p>Some plugins may choose to dynamically break a page's content into separate navigable pages, which can then be reached via deep links. One example of this would be the Listview plugin, which will break a nested UL (or OL) into separate pages, which are each given a data-jq-url attribute so they can be linked to like any normal "page" in jQuery Mobile. However, in order to link to these pages, the page that generates them must first be requested from the server. To make this work, pages that are auto-generated by plugins use the following special data-jq-url structure:
 			<code>&lt;div data-jq-url="page.html&amp;subpageidentifier"&gt;</code></p> 
 
-			<p>So, for example, a page generated by the listview plugin may have an data-jq-url attribute like this: <code>data-url="artists.html&amp;ui-page=listview-1"</code></p> 
+			<p>So, for example, a page generated by the listview plugin may have an data-jq-url attribute like this: <code>data-jq-url="artists.html&amp;ui-page=listview-1"</code></p> 
 
 			<p>When a page is requested, jQuery Mobile knows to split the URL at "&amp;ui-page" and make an HTTP request to the portion of the URL before that key. In the case of the listview example mentioned above, the URL would look like this: http://example.com/artists.html&amp;ui-page=listview-1
 			...and jQuery Mobile would request artists.html, which would then generate its sub-pages, creating the div with data-jq-url="artists.html&amp;ui-page=listview-1", which it will then display as the active page.</p> 

docs/pages/docs-pages.html

@@ -176,7 +176,7 @@ <h2>Back linking</h2>
 		<h2>Redirects and linking to directories</h2>
 		<p>When linking to directory indexes (such as href="typesofcats/" instead of href="typesofcats/index.html"), you must provide a trailing slash. This is because jQuery Mobile assumes the section after the last "/" character in a url is a filename, and it will remove that section when creating base urls from which future pages will be referenced.</p>
 
-		<p>However, you can work around this issue by returning your page div with a <code>data-url</code> attribute already specified. When you do this, jQuery Mobile will use that attribute's value for updating the URL, instead of the url used to request that page. This also allows you to return urls that change as the result of a redirect, for example, you might post a form to "/login.html" but return a page from the url "/account" after a successful submission. This tool allows you to take control of the jQuery Mobile history stack in these situations. Here's an example:</p>
+		<p>However, you can work around this issue by returning your page div with a <code>data-jq-url</code> attribute already specified. When you do this, jQuery Mobile will use that attribute's value for updating the URL, instead of the url used to request that page. This also allows you to return urls that change as the result of a redirect, for example, you might post a form to "/login.html" but return a page from the url "/account" after a successful submission. This tool allows you to take control of the jQuery Mobile history stack in these situations. Here's an example:</p>
 
 		<p>The following link points to "docs-links-urltest/index.html": <a href="docs-links-urltest/index.html">Test Link</a> which is a directory with an index page. The return page will update the hash as "docs/pages/docs-links-urltest/" with a trailing slash. This is done via the data-jq-url attribute in that page's source. Keep in mind that the value will replace the entire hash, and it is up to you to replace it with a URL that actually resolves to the correct page when requested via refresh or deep link.</p>