From 222dff2aab16b1369fa9d8ac72aaaf7600b23539 Mon Sep 17 00:00:00 2001
From: Gabriel Schulhof <gabriel.schulhof@intel.com>
Date: Thu, 28 Jul 2016 22:00:01 +0300
Subject: [PATCH] All: Remove deprecated entries

Fixes gh-395
---
 entries/button.xml                          |   1 -
 entries/buttonMarkup.xml                    | 290 --------------------
 entries/checkboxradio.xml                   |   1 -
 entries/collapsible.xml                     |   1 -
 entries/collapsibleset.xml                  |  20 --
 entries/controlgroup.xml                    |   1 -
 entries/dialog.xml                          | 169 ------------
 entries/fieldcontain.xml                    |  13 -
 entries/jQuery.mobile.activePage.xml        |  10 -
 entries/jQuery.mobile.changePage.xml        | 126 ---------
 entries/jQuery.mobile.getDocumentBase.xml   |  17 --
 entries/jQuery.mobile.getDocumentUrl.xml    |  17 --
 entries/jQuery.mobile.getInheritedTheme.xml |  38 ---
 entries/jQuery.mobile.loadPage.xml          | 113 --------
 entries/listview.xml                        |   1 -
 entries/navbar.xml                          |   1 -
 entries/page.xml                            |   1 -
 entries/panel.xml                           |   1 -
 entries/popup.xml                           |   1 -
 entries/rangeslider.xml                     |   1 -
 entries/selectmenu.xml                      |   1 -
 entries/slider.xml                          |   1 -
 entries/textinput.xml                       |   1 -
 includes/widget-option-initSelector.xml     |  21 --
 pages/data-attribute.html                   |  23 --
 pages/global-config.html                    |  32 ---
 26 files changed, 902 deletions(-)
 delete mode 100644 entries/buttonMarkup.xml
 delete mode 100644 entries/dialog.xml
 delete mode 100644 entries/fieldcontain.xml
 delete mode 100644 entries/jQuery.mobile.activePage.xml
 delete mode 100644 entries/jQuery.mobile.changePage.xml
 delete mode 100644 entries/jQuery.mobile.getDocumentBase.xml
 delete mode 100644 entries/jQuery.mobile.getDocumentUrl.xml
 delete mode 100644 entries/jQuery.mobile.getInheritedTheme.xml
 delete mode 100644 entries/jQuery.mobile.loadPage.xml
 delete mode 100644 includes/widget-option-initSelector.xml

diff --git a/entries/button.xml b/entries/button.xml
index 21b90ad1..734d420e 100644
--- a/entries/button.xml
+++ b/entries/button.xml
@@ -81,7 +81,6 @@ $( "[type='submit']" ).button();
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="inline" default="null (false)">
 			<desc>If set to <code>true</code>, this will make the <placeholder name="name"/> act like an inline <placeholder name="name"/> so the width is determined by the <placeholder name="name"/>'s text. By default, this is null (false) so the <placeholder name="name"/> is full width, regardless of the feedback content. Possible values: true, false.
 				<p>This option is also exposed as a data attribute: <code>data-inline="true"</code>.</p>
diff --git a/entries/buttonMarkup.xml b/entries/buttonMarkup.xml
deleted file mode 100644
index 116a6566..00000000
--- a/entries/buttonMarkup.xml
+++ /dev/null
@@ -1,290 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
-<entry name="buttonMarkup" type="method" return="jQuery" deprecated="1.4.0">
-	<title>.buttonMarkup()</title>
-	<desc>Adds button styling to an element</desc>
-	<longdesc>
-		<div class="warning"><strong>Note:</strong> .buttonMarkup() is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. You can now assign the full range of button style options to your <code>button</code> or <code>a</code> elements by simply adding classes.</div>
-		<p></p>
-		<h2 id="migration">Transition to class-based styling</h2>
-		Keeping in mind the followings will make it easy for you to transition from the button styling based on data attributes to the class-based process:
-		<ul>
-			<li>When using icons, you must always specify an icon position class along with the icon class, because there is no longer a default icon position. In the example below the class <code>ui-btn-icon-left</code> is added to make sure the icon (<code>ui-icon-arrow-r</code>) will be displayed.
-<pre><code><![CDATA[
-<a href="http://example.com/" class="ui-btn ui-icon-arrow-r ui-btn-icon-left ui-corner-all ui-shadow ui-btn-inline">Example</a>
-]]></code></pre>
-			<iframe src="/resources/buttonMarkup/example48.html" style="width:100%;height:90px;border:0px"></iframe>
-			</li>
-			<li>Although the style-related data attributes are deprecated, the data attributes related to linking behavior remain unchanged. In the example below the button is styled using classes, but the data attributes related to linking are retained.
-<pre><code><![CDATA[
-<a href="/" data-rel="external" class="ui-btn ui-corner-all ui-shadow ui-btn-inline ui-icon-home ui-btn-icon-left">Home</a>
-]]></code></pre>
-			<iframe src="/resources/buttonMarkup/example49.html" style="width:100%;height:90px;border:0px"></iframe>
-			</li>
-			<li>We do not recommend mixing styling based on data attributes and class-based styling during the deprecation period.</li>
-		</ul>
-		<h2>Button markup</h2>
-		<p>You can use <code>.buttonMarkup()</code> to style any element as a button that is attractive and useable on a mobile device. It is a convenience function that allows you to manipulate the classes related to button styling. For each element in the set of matched elements this function converts the <code>options</code> parameter to a list of classes to be applied to the element, while respecting the element's existing classes that are not related to button styling. You may also set the parameter <code>overwriteClasses</code> to <code>true</code> for performance reasons. When <code>overwriteClasses</code> is set to <code>true</code> the function discards existing classes and applies the classes corresponding to the options provided.</p>
-
-	<h2>Autoinitialization</h2>
-	<p>The framework will automatically apply button styling to anchors that have the attribute <code>data-role="button"</code> as well as <code>button</code> elements, anchors contained directly in bars and <a href="/controlgroup/">controlgroup</a> widgets. You can specify button styling options via data attributes that you add to the anchor or <code>button</code> element. The data attribute corresponding to each <code>.buttonMarkup()</code> option is documented in the <a href="#buttonMarkup-options-overwriteClasses">options</a> of <code>.buttonMarkup()</code>. The example below shows the markup needed for an anchor-based button.</p>
-
-<pre><code><![CDATA[
-<a href="index.html" data-role="button">Link button</a>
-]]></code></pre>
-
-		<p>Produces this <strong>anchor-based</strong> button:
-		<iframe src="/resources/buttonMarkup/example1.html" style="width:100%;height:90px;border:0px"></iframe></p>
-
-		<p><strong>Button</strong> based button:</p>
-
-	<p><code>.buttonMarkup()</code> also automatically enhances <code>button</code> elements such as the one below:</p>
-
-<pre><code><![CDATA[
-<button>Button element</button>
-]]></code></pre>
-
-		<iframe src="/resources/buttonMarkup/example4.html" style="width:100%;height:90px;border:0px"></iframe>
-
-	<h3>Disabled appearance</h3>
-	<p>You can style an anchor as disabled by adding the class <code>ui-state-disabled</code>.</p>
-	<p><strong>Note:</strong> It is not inherently possible to "disable" anchors. The class <code>ui-state-disabled</code> merely adds styling to make the anchor look disabled. It does not provide the same level of functionality as the <code>disabled</code> attribute of a form button. It may still be possible to follow the anchor using navigation methods that do not involve the pointing device.</p>
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" class="ui-state-disabled">Link button</a>
-]]></code></pre>
-
-		<p>Produces an <strong>anchor-based</strong> button styled as disabled:
-		<iframe src="/resources/buttonMarkup/example2.html" style="width:100%;height:90px;border:0px"></iframe>
-		</p>
-
-	<p>In the case of <code>button</code> elements, you should apply the <code>ui-state-disabled</code> class when you set the <code>button</code> element's <code>disabled</code> attribute:</p>
-<pre><code><![CDATA[
-// Toggle the class ui-state-disabled in conjunction with modifying the value
-// of the button element's "disabled" property
-$( "button#myButton" )
-	.prop( "disabled", isDisabled )
-	.toggleClass( "ui-state-disabled", isDisabled );
-]]></code></pre>
-		<h3>Inline buttons</h3>
-
-		<p>By default, all buttons in the body content are styled as block-level elements so they fill the width of the screen:
-		<iframe src="/resources/buttonMarkup/example20.html" style="width:100%;height:250px;border:0px"></iframe></p>
-
-		<p>If you have multiple buttons that should sit side-by-side on the same line, add the <code>data-inline="true"</code> attribute to each button. This will style the buttons to be the width of their content and float the buttons so they sit on the same line.</p>
-
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" data-inline="true">Cancel</a>
-<a href="index.html" data-role="button" data-inline="true" data-theme="b">Save</a>
-]]></code></pre>
-
-		<iframe src="/resources/buttonMarkup/example22.html" style="width:100%;height:220px;border:0px"></iframe>
-
-		<p>If you want buttons to sit side-by-side but stretch to fill the width of the screen, you can use the content column grids to put normal full-width buttons into 2- or 3-columns.</p>
-
-		<h3>Mini version</h3>
-
-		<p>For a more compact version that is useful in toolbars and tight spaces, add the <code>data-mini="true"</code> attribute to the button to create a mini version. </p>
-
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" data-mini="true">Link button</a>
-]]></code></pre>
-
-		<p>This will produce a button that is not as tall as the standard version and has a smaller text size.
-		<iframe src="/resources/buttonMarkup/example3.html" style="width:100%;height:90px;border:0px"></iframe>
-		</p>
-
-    <h2>Adding Icons to Buttons</h2>
-		<p>The jQuery Mobile framework includes a selected set of icons most often needed for mobile apps. To minimize download size, jQuery Mobile includes a single white icon sprite, and automatically adds a semi-transparent black circle behind the icon to ensure that it has good contrast on any background color.</p>
-
-			<p>An icon can be added to a button by adding a <code>data-icon</code> attribute on the anchor specifying the icon to display. For example:</p>
-
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" data-icon="delete">Delete</a>
-]]></code></pre>
-
-			<iframe src="/resources/buttonMarkup/example8.html" style="width:100%;height:220px;border:0px"></iframe>
-
-			<h3>Icon set</h3>
-
-			<p>The following <code>data-icon</code> attributes can be referenced to create the icons shown below:
-			<iframe src="/resources/buttonMarkup/example10.html" style="width:100%;height:1970px;border:0px"></iframe></p>
-
-			<h3>Icon positioning</h3>
-			<p>By default, all icons in buttons are placed to the left of the button text.
-			<iframe src="/resources/buttonMarkup/example11.html" style="width:100%;height:90px;border:0px"></iframe></p>
-
-			<p>This default may be overridden using the <code>data-iconpos</code> attribute to set the icon to the right, above (top) or below (bottom) the text. For example:</p>
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" data-icon="delete" data-iconpos="right">Delete</a>
-]]></code></pre>
-
-			<iframe src="/resources/buttonMarkup/example12.html" style="width:100%;height:380px;border:0px"></iframe>
-
-			<p>You can also create an icon-only button, by setting the <code>data-iconpos</code> attribute to <code>notext</code>. The button plugin will hide the text on-screen, but add it as a <code>title</code> attribute on the link to provide context for screen readers and devices that support tooltips. For example, replacing <code>data-iconpos="right"</code> on the previous example with <code>data-iconpos="notext"</code>:</p>
-
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" data-icon="delete" data-iconpos="notext">Delete</a>
-]]></code></pre>
-
-			<p>Creates this icon-only button:
-			<iframe src="/resources/buttonMarkup/example15.html" style="width:100%;height:60px;border:0px"></iframe></p>
-
-			<h3>Mini &amp; Inline</h3>
-			<p>The mini and inline attributes can be added to produce more compact buttons:
-			<iframe src="/resources/buttonMarkup/example16.html" style="width:100%;height:90px;border:0px"></iframe></p>
-
-			<h3>Custom Icons</h3>
-			<p>To use custom icons, specify a <code>data-icon</code> value that has a unique name like <code>myapp-email</code> and the button plugin will generate a class by prefixing <code>ui-icon-</code> to the <code>data-icon</code> value and apply it to the button: <code>ui-icon-myapp-email</code>.</p>
-			<p>You can then write a CSS rule in your stylesheet that targets the <code>ui-icon-myapp-email:after</code> class to specify the icon background source. The framework contains an inline (data URI) SVG test and adds class <code>ui-nosvg</code> to the <code>html</code> element if this is not supported. If you are using SVG icons you can use this class to provide a fallback to external PNG icons.</p>
-
-<pre><code><![CDATA[
-.ui-icon-myapp-email:after {
-	background-image: url('data:image/svg+xml;...');
-}
-.ui-nosvg .ui-icon-myapp-email:after {
-	background-image: url( "app-icon-email.png" );
-}
-]]></code></pre>
-
-		<h3>Icons and themes</h3>
-		<p>The semi-transparent black circle behind the white icon ensures good contrast on any background color so it works well with the jQuery Mobile theming system. Here are examples of the same icons sitting on top of a range of different color swatches with themed buttons.</p>
-
-		<p>
-		<iframe src="/resources/buttonMarkup/example17.html" style="width:100%;height:450px;border:0px"></iframe></p>
-
-		<h3>Icon example</h3>
-
-		<iframe src="/resources/buttonMarkup/example24.html" style="width:100%;height:220px;border:0px"></iframe>
-
-		<h2>Grouped buttons</h2>
-
-		<p>Occasionally, you may want to visually group a set of buttons to form a single block that looks contained like a navigation component. To get this effect, wrap a set of buttons in a container with the <code>data-role="controlgroup"</code> attribute - the framework will create a vertical button group, remove all margins and drop shadows between the buttons, and only round the first and last buttons of the set to create the effect that they are grouped together.</p>
-
-<pre><code><![CDATA[
-<div data-role="controlgroup">
-	<a href="index.html" data-role="button">Yes</a>
-	<a href="index.html" data-role="button">No</a>
-	<a href="index.html" data-role="button">Maybe</a>
-</div>
-]]></code></pre>
-
-		<p>By default, grouped buttons are presented as a vertical list:
-		<iframe src="/resources/buttonMarkup/example26.html" style="width:100%;height:150px;border:0px"></iframe></p>
-
-		<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>
-
-		<p>
-		<iframe src="/resources/buttonMarkup/example27.html" style="width:100%;height:550px;border:0px"></iframe></p>
-
-        <h3>Labels</h3>
-		<p>Because the <code>label</code> element will be associated with each individual <code>input</code> or <code>button</code> and will be hidden for styling purposes, we recommend wrapping the buttons in a <code>fieldset</code> element that has a <code>legend</code> which acts as the combined label for the group. Using the <code>label</code> as a wrapper around an input prevents the framework from hiding it, so you have to use the <code>for</code> attribute to associate the <code>label</code> with the input.</p>
-
-		<h2>Theming button-styled elements</h2>
-
-		<p>jQuery Mobile has a rich theming system that gives you full control of how buttons are styled. When a link is added to a container, it is automatically assigned a theme swatch letter that matches its parent bar or content box to visually integrate the button into the parent container, like a chameleon. So a button placed inside a content container with a theme of "a" will be automatically assigned the button theme of "a". Here are examples of the button theme pairings in the default theme. All buttons have the same HTML markup:
-		<iframe src="/resources/buttonMarkup/example33.html" style="width:100%;height:240px;border:0px"></iframe></p>
-
-		<h3>Assigning theme swatches</h3>
-		<p>Buttons can be manually assigned any of the button color swatches from the theme to add visual contrast with the container they sit inside by adding the <code>data-theme</code> attribute on the button markup and specifying a swatch letter.</p>
-
-<pre><code><![CDATA[
-<a href="index.html" data-role="button" data-theme="b">Swatch b</a>
-]]></code></pre>
-
-		<p>Here are 2 buttons with icons that have a different swatch letter assigned via the <code>data-theme</code> attribute.
-		<iframe src="/resources/buttonMarkup/example34.html" style="width:100%;height:90px;border:0px"></iframe></p>
-
-		<h3>Theme variations</h3>
-
-		<p><iframe src="/resources/buttonMarkup/example35.html" style="width:100%;height:330px;border:0px"></iframe></p>
-
-	</longdesc>
-	<signature>
-		<argument name="options" type="Object">
-			<property name="corners" default="true">
-				<desc>Adds the class <code>ui-corner-all</code> when <code>true</code> and removes it when <code>false</code>. This gives the button-styled element rounded corners.
-				<p>This option is also exposed as a data-attribute: <code>data-corners="false"</code></p>
-				<iframe src="/resources/buttonMarkup/example40.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="Boolean" />
-			</property>
-			<property name="icon" default='""'>
-				<desc>Adds an icon class by prefixing the value with the string "ui-icon-" and an icon position class based on the value of the <code>iconpos</code> option.
-				<p>For example, if the value is "arrow-r" and the value of the <code>iconpos</code> option is "left", then <code>.buttonMarkup()</code> will add the classes <code>ui-icon-arrow-r</code> and <code>ui-btn-icon-left</code> to each of the set of matched elements.</p>
-				<p>This option is also exposed as a data-attribute: <code>data-icon="arrow-r"</code></p>
-				<iframe src="/resources/buttonMarkup/example41.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="String" />
-			</property>
-			<property name="iconpos" default='"left"'>
-				<desc>Adds an icon position class by prefixing the value with the string "ui-btn-icon-" when the button-styled element has an icon.
-				<p>For example, if the value is "right" and the button-styled element has an icon, then the class <code>ui-btn-icon-right</code> will be added to each of the set of matched elements.</p>
-				<p>This option is also exposed as a data-attribute: <code>data-iconpos="right"</code></p>
-				<iframe src="/resources/buttonMarkup/example42.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="String" />
-			</property>
-			<property name="iconshadow" default="false" deprecated="1.4.0">
-				<desc>
-					<strong>This option is deprecated in 1.4.0 and will be removed in 1.5.0.</strong>
-					<p>Adds the class <code>ui-shadow-icon</code> to each of the set of matched elements when set to <code>true</code> and the button-styled element has an icon.</p>
-				<p>This option is also exposed as a data-attribute: <code>data-iconshadow="true"</code></p>
-				<iframe src="/resources/buttonMarkup/example43.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="Boolean" />
-			</property>
-			<property name="inline" default="false">
-				<desc>
-					Adds the class <code>ui-btn-inline</code> to each of the set of matched elements when set to true.
-				<p>This option is also exposed as a data-attribute: <code>data-inline="true"</code></p>
-				<iframe src="/resources/buttonMarkup/example44.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="Boolean" />
-			</property>
-			<property name="mini" default="false">
-				<desc>
-					Adds the class <code>ui-mini</code> to each of the set of matched elements when set to true.
-				<p>This option is also exposed as a data-attribute: <code>data-mini="true"</code></p>
-				<iframe src="/resources/buttonMarkup/example45.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<tyle name="Boolean" />
-			</property>
-			<property name="shadow" default="true">
-				<desc>
-					Adds the class <code>ui-shadow</code> to each of the set of matched elements when set to true.
-				<p>This option is also exposed as a data-attribute: <code>data-shadow="false"</code></p>
-				<iframe src="/resources/buttonMarkup/example46.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="Boolean" />
-			</property>
-			<property name="theme" default="null, inherited from parent">
-				<desc>
-					The value is a letter a-z identifying one of the color swatches in the current theme, or <code>null</code>.
-					<p>This option adds a class constructed by appending the string "ui-btn-" to the value to each of the set of matched elements. If set to <code>null</code>, no class is added, and the swatch is inherited from the element's parent.</p>
-					<p>For example, a value of "b" will cause the class <code>ui-btn-b</code> to be added to each of the set of matched elements.</p>
-				<p>This option is also exposed as a data-attribute: <code>data-theme="b"</code></p>
-				<iframe src="/resources/buttonMarkup/example47.html" style="width:100%;height:90px;border:0px"></iframe>
-				</desc>
-				<type name="String" />
-			</property>
-		</argument>
-		<argument name="overwriteClasses" default="false">
-			<desc>
-				When set to <code>true</code>, <code>.buttonMarkup()</code> discards all classes on each of the set of matched elements and adds classes based on the values passed into the <code>options</code> argument. You can use this feature to increase performance in situations where the element you wish to enhance does not have any classes other than the button styling classes added by <code>.buttonMarkup()</code>.
-				<p>Conversely, when set to <code>false</code>, <code>.buttonMarkup()</code> first parses the existing classes found on each of the set of matched elements and computes a set of existing options based on the presence or absence of classes related to button styling already present. It separately records any classes unrelated to button styling. It then merges the options specified in the <code>options</code> parameter with the computed options such that the <code>options</code> passed in take precedence, and calculates a list of classes that must be present for those options to be expressed in the element's styling. It then re-applies the classes unrelated to button styling as well as the classes that reflect the new set of options. This means that calling <code>.buttonMarkup()</code> on the same element multiple times will have the expected effect:</p>
-<pre><code><![CDATA[
-// Initially corners are turned off
-$( "#myAnchor" ).buttonMarkup({ corners: false });
-
-// Later on we turn off shadow - the lack of corners is retained
-$( "#myAnchor" ).buttonMarkup({ shadow: false });
-
-// Later still we turn corners back on - the lack of shadow is retained
-$( "#myAnchor" ).buttonMarkup({ corners: true });
-]]></code></pre>
-			</desc>
-			<type name="Boolean" />
-		</argument>
-	</signature>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/checkboxradio.xml b/entries/checkboxradio.xml
index 1695487c..1afcfaf1 100644
--- a/entries/checkboxradio.xml
+++ b/entries/checkboxradio.xml
@@ -208,7 +208,6 @@
 			</desc>
 			<type name="String" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-mini.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="wrapperClass" default="null" example-value='"custom-class"'>
 			<desc>It is difficult to write custom CSS for the wrapper <code>div</code> around the native <code>input</code> element generated by the framework. This option allows you to specify one or more space-separated class names to be added to the wrapper <code>div</code> element by the framework.
diff --git a/entries/collapsible.xml b/entries/collapsible.xml
index b9c84108..a4192538 100644
--- a/entries/collapsible.xml
+++ b/entries/collapsible.xml
@@ -194,7 +194,6 @@
 			</desc>
 			<type name="String" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="inset" default="true" example-value="false">
 			<desc>By setting this option to false the element will get a full width appearance without corners.
 				<p>If the value is unset for an individual collapsible container, but that container is part of a collapsible set, then the value is inherited from the parent collapsible set.</p>
diff --git a/entries/collapsibleset.xml b/entries/collapsibleset.xml
index 5e319276..9075662c 100644
--- a/entries/collapsibleset.xml
+++ b/entries/collapsibleset.xml
@@ -120,25 +120,6 @@
 			</desc>
 			<type name="String" />
 		</option>
-		<option name="initSelector" default="null" deprecated="1.4.0">
-			<desc>
-				<p>The default <code>initSelector</code> for the <placeholder name="name" /> widget is:</p>
-		<pre><code>
-		"<placeholder name="init-selector"/>"
-		</code></pre>
-				<p><strong>This option is deprecated in 1.4.0 and will be removed in 1.5.0.</strong></p>
-				<p><strong>The old value of the <placeholder name="name" /> widget's <code>initSelector</code> option (<code>":jqmData(role='collapsible-set')"</code>) is deprecated.</strong> As of jQuery Mobile 1.5.0, only widgets that have the attribute <code>data-role="collapsibleset"</code> will be enhanced as <placeholder name="name"/> widgets.</p>
-				<p>As of jQuery Mobile 1.4.0, the <code>initSelector</code> is no longer a widget option. Instead, it is declared directly on the widget prototype. Thus, you may specify a custom value by handling the <code>mobileinit</code> event and overwriting the <code>initSelector</code> on the prototype:</p>
-		<pre><code>
-		$( document ).on( "mobileinit", function() {
-			$.mobile.<placeholder name="name"/>.prototype.initSelector = "div.custom";
-		});
-		</code></pre>
-				<p><strong>Note:</strong> Remember to attach the <code>mobileinit</code> handler after you have loaded jQuery, but before you load jQuery Mobile, because the event is triggered as part of jQuery Mobile's loading process.</p>
-				<p>The value of this option is a jQuery selector string. The framework selects elements based on the value of this option and instantiates <placeholder name="name" /> widgets on each of the resulting list of elements.</p>
-			</desc>
-			<type name="String" />
-		</option>
 		<option name="inset" default="true" example-value="false">
 			<desc>By setting this option to false the collapsibles will get a full width appearance without corners. If the value is false for an individual collapsible container, but that container is part of a <placeholder name="name"/> widget, then the value is inherited from the parent <placeholder name="name"/> widget.
 				<p>This option is also exposed as a data attribute: <code>data-inset="true"</code>.</p>
@@ -151,7 +132,6 @@
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 	</options>
 	<events>
 		<xi:include href="../includes/widget-event-create.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
diff --git a/entries/controlgroup.xml b/entries/controlgroup.xml
index 6dbd4178..e7dfce2a 100644
--- a/entries/controlgroup.xml
+++ b/entries/controlgroup.xml
@@ -45,7 +45,6 @@
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-mini.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="shadow" default="false" example-value="true">
 			<desc>
diff --git a/entries/dialog.xml b/entries/dialog.xml
deleted file mode 100644
index 06e8b7e6..00000000
--- a/entries/dialog.xml
+++ /dev/null
@@ -1,169 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
-<entry name="dialog" namespace="fn" type="widget" widgetnamespace="mobile" event-prefix="dialog" init-selector=":jqmData(role=&#39;dialog&#39;)" deprecated="1.4.0">
-	<title>Dialog Widget</title>
-	<desc>Opens content in an interactive overlay.</desc>
-	<longdesc>
-		<div class="warning">
-		<strong>Note:</strong> Dialogs are deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. The <code>dialog</code> option provided by the <code>page.dialog</code> extension of the <a href="/page/">page</a> widget allows you to style a page as a dialog, however, the special navigational handling will be removed. You may also consider implementing dialogs using <a href="/popup/">popup</a> widgets.</div>
-		<p>Any page can be presented as a modal dialog by adding the <code>data-rel="dialog"</code> attribute to the page anchor link. When the "dialog" attribute is applied, the framework adds styles to add rounded corners, margins around the page and a dark background to make the "dialog" appear to be suspended above the page.</p>
-<pre><code><![CDATA[
-<a href="foo.html" data-rel="dialog">Open dialog</a>
-]]></code></pre>
-
-		<iframe src="/resources/dialog/example1.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<p>You can open a dialog programmatically by calling the <a href="/jQuery.mobile.changePage/"><strong>$.mobile.changePage</strong></a> method:</p>
-<pre><code><![CDATA[
-// Dialog loaded via Ajax
-$.mobile.changePage( "path/to/dialog.html", { role: "dialog" } );
-
-// Dialog present in a multipage document
-$.mobile.changePage( "#myDialog", { role: "dialog" } );
-]]></code></pre>
-
-		<h3>Transitions</h3>
-
-		<p>By default, the dialog will open with a 'pop' transition. Like all pages, you can specify any page transition you want on the dialog by adding the <code>data-transition</code> attribute to the link. To make it feel more dialog-like, we recommend specifying a transition of "pop", "slidedown" or "flip".<br />Possible values include: fade, <b>pop</b>, <b>flip</b>, turn, flow, slidefade, slide, slideup, slidedown, none. </p>
-
-<pre><code><![CDATA[
-<a href="foo.html" data-rel="dialog" data-transition="pop">Open dialog</a>
-]]></code></pre>
-
-		<iframe src="/resources/dialog/example2.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<h3>Closing dialogs</h3>
-
-		<p>When any link is clicked within a dialog, the framework will automatically close the dialog and transition to the requested page, just as if the dialog were a normal page. Nevertheless, dialogs can also be chained, as explained below under <b>"Chaining Dialogs"</b>. Similarly, a link that opens a popup will also leave the dialog in place.</p>
-
-		<p>If the dialog has a header the framework will add a close button at the left side of the header. You can change the position by adding <code>data-close-btn="right"</code> to the dialog container. If you don't want a close button in the header or add a custom close button, you can use <code>data-close-btn="none"</code>.</p>
-
-		<iframe src="/resources/dialog/example6.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<p>To create a "cancel" button in a dialog, just link to the page that triggered the dialog to open and add the <code>data-rel="back"</code> attribute to your link. This pattern of linking to the previous page is also usable in non-JS devices as well.</p>
-
-		<p>For JavaScript-generated links, you can simply set the href attribute to "#" and use the <code>data-rel="back"</code> attribute. You can also call the dialog's <code>close()</code> method to programmatically close dialogs, for example: <code>$( ".ui-dialog" ).dialog( "close" ). </code></p>
-
-		<h3>Setting the close button text</h3>
-
-		<p>Just like the page plugin, you can set a dialog's close button text through an option or data attribute. The option can be configured for all dialogs by binding to the <code>mobileinit</code> event and setting the <code>$.mobile.dialog.prototype.options.closeBtnText</code> property to a string of your choosing, or you can place the data attribute <code>data-close-btn-text</code> to configure the text from your markup.</p>
-
-		<h3>History &amp; Back button behavior</h3>
-
-		<p>Since dialogs are typically used to support actions within a page, the framework does not include dialogs in the hash state history tracking. This means that dialogs will not appear in your browsing history chronology when the Back button is clicked. For example, if you are on a page, click a link to open a dialog, close the dialog, then navigate to another page, if you were to click the browser's Back button at that point you will navigate back to the first page, not the dialog.</p>
-
-		<h3>Chaining Dialogs</h3>
-
-		<p>Please note: If a dialog opens another dialog (chaining), closing the last one with a link of type <code>data-rel="back"</code> will always navigate to the previous dialog until the root-page of type <code>data-role="page"</code> is reached. This guarantees a consistent navigation between dialogs.</p>
-
-		<h3>Styling &amp; theming</h3>
-
-		<p>Dialogs can be styled with different theme swatches, just like any page by adding <code>data-theme</code> attributes to the header, content, or footer containers.</p>
-
-		<iframe src="/resources/dialog/example3.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<p>By default dialogs have rounded corners. The option corners can be set to false by adding <code>data-corners="false"</code> to the dialog container:</p>
-
-		<iframe src="/resources/dialog/example7.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<p>Dialogs appear to be floating above an overlay layer. This overlay adopts the swatch 'a' content color by default, but the <code>data-overlay-theme</code> attribute can be added to the page wrapper to set the overlay to any swatch letter. </p>
-
-		<iframe src="/resources/dialog/example4.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<p>Dialogs can also be used more like a control sheet to offer multiple buttons if you simply remove the top margin from the dialog's inner container element. For example, if your dialog page had a class of <code>my-dialog</code>, you could add this CSS to pin that dialog to the top: <code>.ui-dialog.my-dialog .ui-dialog-contain { margin-top: 0 }</code>, or you could just apply that style to all dialogs with <code>.ui-dialog .ui-dialog-contain { margin-top: 0 }</code>.</p>
-
-		<iframe src="/resources/dialog/example5.html" style="width:100%;height:420px;border:0px"></iframe>
-
-		<h3>Dialog width and margins</h3>
-
-		<p>For the sake of readability, dialogs have a default <code>width</code> of 92.5% and a <code>max-width</code> of 500 pixels. There is also a 10% top <code>margin</code> to give dialogs larger top margin on larger screens, but collapse to a small margin on smartphones. The dialog's inner container is shifted towards the <code>top</code> with 15px to hide the corner styling if a dialog is used as a control sheet (see above). To override these styles, add the following CSS override rule to your stylesheet and tweak as needed:</p>
-
-<pre><code><![CDATA[
-.ui-dialog-contain {
-	width: 92.5%;
-	max-width: 500px;
-	margin: 10% auto 15px auto;
-	padding: 0;
-	position: relative;
-	top: -15px;
-}
-]]></code></pre>
-
-	</longdesc>
-	<added>1.0</added>
-	<options>
-		<option name="closeBtn" default='"left"' example-value='"none"'>
-			<desc>
-				<p>Sets the position of the dialog close button in the header (left or right) or prevents the framework from adding a close button (none).</p>
-				<p>This option is also exposed as a data attribute: <code>data-close-btn</code>.</p>
-			</desc>
-			<type name="String" />
-		</option>
-		<option name="closeBtnText" default='"Close"' example-value='"Fermer"'>
-			<desc>
-				<p>Customizes the text of the close button which is helpful for translating this into different languages. The close button is displayed as an icon-only button by default so the text isn't visible on-screen, but is read by screen readers so this is an important accessibility feature.</p>
-				<p>This option is also exposed as a data attribute: <code>data-close-btn-text="Fermer"</code>.</p>
-			</desc>
-			<type name="String" />
-		</option>
-		<option name="corners" default="true" example-value="false">
-			<desc>Sets whether to draw the dialo with rounded corners..
-				<p>This option is also exposed as a data attribute:<code>data-corners="false"</code>.</p>
-			</desc>
-			<type name="Boolean" />
-		</option>
-		<xi:include href="../includes/widget-option-defaults.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
-		<xi:include href="../includes/widget-option-disabled.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
-		<option name="overlayTheme" default='"a"' example-value='"b"'>
-			<desc>
-				<p>Dialogs appear to be floating above an overlay layer. This overlay adopts the swatch A content color by default, but the data-overlay-theme attribute can be added to the page wrapper to set the overlay to any swatch letter.</p>
-				<p> Possible values: swatch letter (a-z)</p>
-				<p>This option is also exposed as a data attribute: <code>data-overlay-theme="b"</code>.</p>
-			</desc>
-			<type name="String" />
-		</option>
-	</options>
-	<events>
-		<event name="create">
-			<desc>Triggered when a dialog is created</desc>
-			<argument name="event" type="Event">
-				<desc></desc>
-			</argument>
-			<argument name="ui" type="Object">
-				<desc></desc>
-			</argument>
-		</event>
-	</events>
-	<methods>
-		<method name="close">
-			<desc>Closes the dialog.</desc>
-		</method>
-	</methods>
-	<example>
-		<desc>A basic example of opening a page as a dialog by adding <code>data-rel="dialog"</code> to the anchor tag.</desc>
-		<html><![CDATA[
-<div data-role="page" id="page1">
-	<div data-role="header">
-		<h1>jQuery Mobile Example</h1>
-	</div>
-	<div role="main" class="ui-content">
-		<a href="#dialogPage" data-rel="dialog">Open dialog</a>
-	</div>
-	<div data-role="footer">
-		<h2></h2>
-	</div>
-</div>
-
-<div data-role="page" id="dialogPage">
-	<div data-role="header">
-		<h2>Dialog</h2>
-	</div>
-	<div role="main" class="ui-content">
-		<p>I am a dialog</p>
-	</div>
-</div>
-]]></html>
-	</example>
-	<category slug="widgets"/>
-</entry>
diff --git a/entries/fieldcontain.xml b/entries/fieldcontain.xml
deleted file mode 100644
index efe218f5..00000000
--- a/entries/fieldcontain.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
-<entry name="fieldcontain" type="method" return="jQuery" deprecated="1.4.0">
-	<title>.fieldcontain()</title>
-	<desc>Adds field container styling to an element</desc>
-	<longdesc>
-		<div class="warning">
-			<p><strong>Note:</strong> .fieldcontain() is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. You can now construct responsive multi-field forms by wrapping each form element and its label in a <code>div</code> with class <code>ui-field-contain</code>.</p>
-		</div>
-		<p>Adds class <code>ui-field-contain</code> to <code>div</code> wrappers of individual form elements which have a label. The <code>div</code> and the class ensure that the form is rendered responsively. At a sufficient width the label for each form element will be placed to the left of the form element, whereas on narrow displays, the label will appear above the form element.</p>
-	</longdesc>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/jQuery.mobile.activePage.xml b/entries/jQuery.mobile.activePage.xml
deleted file mode 100644
index 10428494..00000000
--- a/entries/jQuery.mobile.activePage.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<entry type="property" name="jQuery.mobile.activePage" return="jQuery" deprecated="1.4.0">
-	<title>jQuery.mobile.activePage</title>
-	<desc>Reference to the page currently in view.</desc>
-	<longdesc>
-		<div class="warning"><strong>Note:</strong> <placeholder name="name"/> is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Use the <a href="/pagecontainer/#method-getActivePage">getActivePage()</a> method from the <code>pagecontainer</code> widget instead.</div>
-	</longdesc>
-	<added>1.0</added>
-	<category slug="properties"/>
-</entry>
diff --git a/entries/jQuery.mobile.changePage.xml b/entries/jQuery.mobile.changePage.xml
deleted file mode 100644
index e1401a2f..00000000
--- a/entries/jQuery.mobile.changePage.xml
+++ /dev/null
@@ -1,126 +0,0 @@
-<?xml version="1.0"?>
-<entry type="method" name="jQuery.mobile.changePage" return="Undefined" deprecated="1.4.0">
-	<title>jQuery.mobile.changePage()</title>
-	<desc>Programmatically change from one page to another.
-		<div class="warning">
-			<p><strong>Note:</strong> <placeholder name="name"/> is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Use the <a href="/pagecontainer/">pagecontainer</a> widget's <a href="/pagecontainer/#method-change">change()</a> method instead.</p>
-		</div>
-	</desc>
-	<signature>
-		<argument name="to">
-			<type name="String">
-				<desc>Absolute or relative URL. ( "about/us.html" )</desc>
-			</type>
-			<type name="Object">
-				<desc>jQuery collection object. ( $( "#about" ) )</desc>
-			</type>
-		</argument>
-		<argument name="options" type="Object" optional="true">
-			<desc>Properties:</desc>
-			<property name="allowSamePageTransition" type="Boolean" default="false">
-				<desc>By default, changePage() ignores requests to change to the current active page. Setting this option to true, allows the request to execute. Developers should note that some of the page transitions assume that the fromPage and toPage of a changePage request are different, so they may not animate as expected. Developers are responsible for either providing a proper transition, or turning it off for this specific case.
-				</desc>
-			</property>
-			<property name="changeHash" type="Boolean" default="true">
-				<desc>Decides if the hash in the location bar should be updated. This has the effect of creating a new browser history entry. It also means that, if set to <strong>false</strong>, the incoming page will replace the current page in the browser history, so the page from which the user is navigating away will not be reachable via the browser's "Back" button.</desc>
-			</property>
-			<property name="data" default="undefined">
-				<desc>The data to send with an Ajax page request.<br />Used only when the 'to' argument of changePage() is a URL.</desc>
-				<type name="Object">
-					<desc></desc>
-				</type>
-				<type name="String">
-					<desc></desc>
-				</type>
-			</property>
-			<property name="dataUrl" type="String" default="undefined">
-				<desc>The URL to use when updating the browser location upon changePage completion. If not specified, the value of the data-url attribute of the page element is used.</desc>
-			</property>
-			<property name="pageContainer" type="jQuery collection" default="$.mobile.pageContainer">
-				<desc>Specifies the element that should contain the page.</desc>
-			</property>
-			<property name="reloadPage" type="Boolean" default="false">
-				<desc>Forces a reload of a page, even if it is already in the DOM of the page container. <br />Used only when the 'to' argument of changePage() is a URL.</desc>
-			</property>
-			<property name="reverse" type="Boolean" default="false">
-				<desc>Decides what direction the transition will run when showing the page.</desc>
-			</property>
-			<property name="role" type="String" default="undefined">
-				<desc>The data-role value to be used when displaying the page. By default this is undefined which means rely on the value of the @data-role attribute defined on the element.</desc>
-			</property>
-			<property name="showLoadMsg" type="Boolean" default="true">
-				<desc>Decides whether or not to show the loading message when loading external pages.</desc>
-			</property>
-			<property name="transition" type="String" default="$.mobile.defaultPageTransition">
-				<desc>The transition to use when showing the page. </desc>
-			</property>
-			<property name="type" type="String" default='"get"'>
-				<desc>Specifies the method (&quot;get&quot; or &quot;post&quot;) to use when making a page request. <br />Used only when the 'to' argument of changePage() is a URL.</desc>
-			</property>
-		</argument>
-	</signature>
-	<example>
-		<desc>Transition to the "about us" page with a slideup transition.</desc>
-		<html><![CDATA[
-<div data-role="page" id="page1">
-	<div data-role="header">
-		<h1>Page 1</h1>
-	</div>
-	<div role="main" class="ui-content">
-	</div>
-</div>
-]]></html>
-		<code><![CDATA[
-//Adding the changeHash: false to avoid an issue with the iframe
-$.mobile.changePage( "../resources/us.html", { transition: "slideup", changeHash: false });
-]]></code>
-		</example>
-		<example>
-			<desc>Transition to the "search results" page, using data from a form with an id of "search".</desc>
-			<html><![CDATA[
-<div data-role="page" id="page1">
-	<div data-role="header">
-		<h1>Page 1</h1>
-	</div>
-	<div role="main" class="ui-content">
-		<form id="search">
-			<p>Please fill in the form below:<br /><br />
-			<label for="choice">Favorite framework:</label>
-			<input type="text" name="choice" id="choice" value="jQuery Mobile" />
-			</p>
-		</form>
-	</div>
-</div>
-]]></html>
-		<code><![CDATA[
-$.mobile.changePage( "../resources/results.php", {
-	type: "post",
-	data: $( "form#search" ).serialize(),
-	changeHash: false
-});
-]]></code>
-	</example>
-	<example>
-		<desc>Transition to the "confirm" page with a "pop" transition without tracking it in history.</desc>
-		<html><![CDATA[
-<div data-role="page" id="page1">
-	<div data-role="header">
-		<h1>Page 1</h1>
-	</div>
-	<div role="main" class="ui-content">
-	</div>
-</div>
-]]></html>
-		<code><![CDATA[
-$.mobile.changePage( "../resources/confirm.html", {
-	transition: "pop",
-	reverse: false,
-	changeHash: false
-});
-]]></code>
-	</example>
-	<longdesc>
-		<p>Programmatically change from one page to another. This method is used internally for the page loading and transitioning that occurs as a result of clicking a link or submitting a form, when those features are enabled.</p>
-	</longdesc>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/jQuery.mobile.getDocumentBase.xml b/entries/jQuery.mobile.getDocumentBase.xml
deleted file mode 100644
index 576e915b..00000000
--- a/entries/jQuery.mobile.getDocumentBase.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<entry type="method" name="jQuery.mobile.getDocumentBase" deprecated="1.4.0">
-	<title>jQuery.mobile.getDocumentBase()</title>
-	<desc>Utility method for retrieving the original document base URL.
-		<div class="warning">
-			<p><strong>Note:</strong> <placeholder name="name"/> is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Use the <a href="/jQuery.mobile.path.getDocumentBase/">jQuery.mobile.path.getDocumentBase()</a> method instead.</p>
-		</div>
-	</desc>
-	<signature>
-		<argument name="asParsedObject" type="Boolean" default="false">
-			<desc>
-				The function normally returns the original document base URL as a string. However, if you specify a truthy value for this parameter, the original document base URL will be returned in a hash as a parsed URL.
-			</desc>
-		</argument>
-	</signature>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/jQuery.mobile.getDocumentUrl.xml b/entries/jQuery.mobile.getDocumentUrl.xml
deleted file mode 100644
index 169c8af4..00000000
--- a/entries/jQuery.mobile.getDocumentUrl.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<entry type="method" name="jQuery.mobile.getDocumentUrl" return="String" deprecated="1.4.0">
-	<title>jQuery.mobile.getDocumentUrl()</title>
-	<desc>Retrieve the URL of the original document.
-		<div class="warning">
-			<p><strong>Note:</strong> <placeholder name="name"/> is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Use the <a href="/jQuery.mobile.path.getDocumentUrl/">jQuery.mobile.path.getDocumentUrl()</a> method instead.</p>
-		</div>
-	</desc>
-	<signature>
-		<argument name="asParsedObject" type="Boolean" default="false">
-			<desc>
-				The function normally returns the original document's URL as a string. However, if you specify a truthy value for this parameter, the original document's URL will be returned in a hash as a parsed URL.
-			</desc>
-		</argument>
-	</signature>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/jQuery.mobile.getInheritedTheme.xml b/entries/jQuery.mobile.getInheritedTheme.xml
deleted file mode 100644
index 796a4c16..00000000
--- a/entries/jQuery.mobile.getInheritedTheme.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0"?>
-<entry type="method" name="jQuery.mobile.getInheritedTheme" return="String" deprecated="1.4.0">
-	<title>jQuery.mobile.getInheritedTheme()</title>
-	<desc>Retrieves the theme of the nearest parent that has a theme assigned.</desc>
-	<longdesc>
-		<p>This method is no longer useful, since theme inheritance is implemented entirely in CSS as of jQuery Mobile 1.4.0.</p>
-	</longdesc>
-	<signature>
-		<argument name="el" type="jQuery">
-			<desc>A jQuery collection object containing an element for which the inherited theme is to be determined.</desc>
-		</argument>
-		<argument name="defaultTheme" type="String">
-			<desc>
-				The color scheme (swatch) to apply if no theme is found on any of the parents. It accepts a single letter from a-z that maps to the swatches included in your theme.
-				<p>Possible values: swatch letter (a-z).</p>
-			</desc>
-		</argument>
-	</signature>
-		<example>
-			<desc>Retrieve the inherited theme for an element</desc>
-				<html><![CDATA[
-	<script>
-	$.mobile.document.on( "click", "#check-theme", function() {
-		alert( "I inherit theme '" +
-			$.mobile.getInheritedTheme( $( this ), "x" ) + "'" );
-	});
-	</script>
-	<div data-role="header">
-		<h2>jQuery Mobile Example</h2>
-	</div>
-	<div role="main" class="ui-content">
-		<p>Click the button below to find out what theme it inherits.</p>
-		<a href="#" id="check-theme" class="ui-btn ui-corner-all ui-shadow">Check my theme</a> 
-	</div>
-				]]></html>
-		</example>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/jQuery.mobile.loadPage.xml b/entries/jQuery.mobile.loadPage.xml
deleted file mode 100644
index ffeef739..00000000
--- a/entries/jQuery.mobile.loadPage.xml
+++ /dev/null
@@ -1,113 +0,0 @@
-<?xml version="1.0"?>
-<entry type="method" name="jQuery.mobile.loadPage" return="Promise" deprecated="1.4.0">
-	<title>jQuery.mobile.loadPage()</title>
-	<desc>Load an external page, enhance its content, and insert it into the DOM.
-		<div class="warning">
-			<p><strong>Note:</strong> <placeholder name="name"/> is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Use the <a href="/pagecontainer/">pagecontainer</a> widget's <a href="/pagecontainer/#method-load">load()</a> method instead.</p>
-		</div>
-	</desc>
-	<signature>
-		<argument name="url">
-			<type name="String">
-				<desc>Absolute or relative URL. ( "about/us.html" )</desc>
-			</type>
-			<type name="Object">
-				<desc>jQuery collection object. ( $( "#about" ) )</desc>
-			</type>
-		</argument>
-		<argument name="options" type="Object" optional="true">
-			<desc>Properties:</desc>
-				<property name="allowSamePageTransition" type="Boolean" default="false">
-					<desc>By default, changePage() ignores requests to change to the current active page. Setting this option to true, allows the request to execute. Developers should note that some of the page transitions assume that the fromPage and toPage of a changePage request are different, so they may not animate as expected. Developers are responsible for either providing a proper transition, or turning it off for this specific case.
-					</desc>
-				</property>
-				<property name="changeHash" type="Boolean" default="true">
-					<desc>Decides if the hash in the location bar should be updated. </desc>
-				</property>
-				<property name="data" default="undefined">
-					<desc>The data to send with an Ajax page request.</desc>
-					<type name="Object">
-						<desc></desc>
-					</type>
-					<type name="String">
-						<desc></desc>
-					</type>
-				</property>
-				<property name="loadMsgDelay" type="Number" default="50">
-					<desc>Forced delay (in ms) before the loading message is shown. This is meant to allow time for a page that has already been visited to be fetched from cache without a loading message.</desc>
-				</property>
-				<property name="pageContainer" type="jQuery collection" default="$.mobile.pageContainer">
-					<desc>Specifies the element that should contain the page.</desc>
-				</property>
-				<property name="reloadPage" type="Boolean" default="false">
-					<desc>Forces a reload of a page, even if it is already in the DOM of the page container. <br />Used only when the 'to' argument of changePage() is a URL.</desc>
-				</property>
-				<property name="role" type="String" default="undefined">
-					<desc>The data-role value to be used when displaying the page. By default this is undefined which means rely on the value of the @data-role attribute defined on the element.</desc>
-				</property>
-				<property name="showLoadMsg" type="Boolean" default="true">
-					<desc>Decides whether or not to show the loading message when loading external pages.</desc>
-				</property>
-				<property name="transition" type="String" default="$.mobile.defaultPageTransition">
-					<desc>The transition to use when showing the page. </desc>
-				</property>
-				<property name="type" type="String" default='"get"'>
-					<desc>Specifies the method (&quot;get&quot; or &quot;post&quot;) to use when making a page request. <br />Used only when the 'to' argument of changePage() is a URL.</desc>
-				</property>
-			</argument>
-	</signature>
-		<example>
-			<desc>Load the "about us" page into the DOM.</desc>
-				<html><![CDATA[
-	<div data-role="header">
-      <h1>loadPage() demo</h1>
-    </div><!-- /header -->
-
-	<div role="main" class="ui-content">
-
-		<p>First check if the 'About us' page is in the DOM, Load the page in the DOM and check again</p>
-		<input type="button" id="domcheck" data-inline="true" value="Is 'About us' in the DOM?"/>
-		<input type="button" id="loadpage" data-inline="true" value="Load the 'About us' page"/><br />
-		<div id="myResult">'About Us' is in the DOM: <span id="result">The result will be displayed here</span></div>
-	</div>
-	]]></html>
-			<code><![CDATA[
-	$( "#domcheck" ).on( "click", function() {
-		var check = $( "#aboutUs" ).length === 1;
-		$( "#result" ).text( check );
-	});
-	$( "#loadpage" ).on( "click", function() {
-		$.mobile.loadPage( "../resources/us.html");
-	});
-]]></code>
-		</example>
-		<example>
-			<desc>Load a "search results" page, using data from a form with an id of "search".</desc>
-			<html><![CDATA[
-	<div role="main" class="ui-content">
-	
-		<form id="search">
-			<p>Please fill in the form below:<br /><br />
-			<label for="choice">Favorite framework:</label>
-			<input type="text" name="choice" id="choice" value="jQuery Mobile" />
-
-			<a href="#formResults" data-role="button" data-inline="true" data-rel="dialog">Show Results</a>
-			</p>
-		</form>
-		
-	</div>
-			]]></html>
-			<code><![CDATA[
-$.mobile.loadPage( "../resources/results.php", true, {
-	type: "post",
-	data: $( "form#search" ).serialize()
-});
-]]></code>
-		</example>
-	<longdesc>
-		<p>Load an external page, enhance its content, and insert it into the DOM. This method is called internally by the changePage() function when its first argument is a URL. This function does not affect the current active page so it can be used to load pages in the background. The function returns a deferred promise object that gets resolved after the page has been enhanced and inserted into the document.
-
-</p>
-	</longdesc>
-	<category slug="methods"/>
-</entry>
diff --git a/entries/listview.xml b/entries/listview.xml
index f07be23a..43e4027c 100644
--- a/entries/listview.xml
+++ b/entries/listview.xml
@@ -239,7 +239,6 @@ $( document ).on( "mobileinit", function() {
 			</desc>
 			<type name="String" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="inset" default="false" example-value="true">
 			<desc>Adds inset list styles.
 				<p>This option is also exposed as a data attribute: <code>data-inset="true"</code>.</p>
diff --git a/entries/navbar.xml b/entries/navbar.xml
index 6738d95a..0791c689 100644
--- a/entries/navbar.xml
+++ b/entries/navbar.xml
@@ -120,7 +120,6 @@
 			</desc>
 		<type name="String" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 	</options>
 	<events>
 		<event name="create">
diff --git a/entries/page.xml b/entries/page.xml
index 9287ca54..b9028ba5 100644
--- a/entries/page.xml
+++ b/entries/page.xml
@@ -110,7 +110,6 @@ $.mobile.back();
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="keepNative" default="null" example-value='".do-not-enhance"' deprecated="1.4.0">
 			<desc>
 				<div class="warning">
diff --git a/entries/panel.xml b/entries/panel.xml
index a38ad4a0..a3470951 100644
--- a/entries/panel.xml
+++ b/entries/panel.xml
@@ -336,7 +336,6 @@ $( "#idofpanel" ).panel( "close" );
 			</desc>
 			<type name="String" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="position" default='"left"'  example-value='"right"'>
 			<desc>The side of the screen the panel appears on. Values can be "left" or "right".
 				<p>This option is also exposed as a data attribute:<code>data-position="right"</code> on the link that opens the panel.</p>
diff --git a/entries/popup.xml b/entries/popup.xml
index 1bfe0697..f306d8c8 100644
--- a/entries/popup.xml
+++ b/entries/popup.xml
@@ -437,7 +437,6 @@ $( document ).on( "pageinit", function() {
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="overlayTheme" default="null" example-value='"b"'>
 			<desc>
 				<p>Sets the color scheme (swatch) for the popup background, which covers the entire window. If not explicitly set, the background will be transparent.</p>
diff --git a/entries/rangeslider.xml b/entries/rangeslider.xml
index 3b304d24..a2dc667c 100644
--- a/entries/rangeslider.xml
+++ b/entries/rangeslider.xml
@@ -129,7 +129,6 @@ $( "div#range-slider" ).rangeslider();
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-mini.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-theme.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="trackTheme" default="null, inherited from parent" example-value='"a"'>
diff --git a/entries/selectmenu.xml b/entries/selectmenu.xml
index 18cba987..b191283d 100644
--- a/entries/selectmenu.xml
+++ b/entries/selectmenu.xml
@@ -290,7 +290,6 @@ $( "select" ).selectmenu();
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="inline" default="null (false)" example-value="true">
 			<desc>If set to true, this will make the select button act like an inline button so the width is determined by the button's text. By default, this is null (false) so the select button is full width, regardless of the feedback content. Possible values: true, false.
 				<p>This option is also exposed as a data attribute: <code>data-inline="true"</code>.</p>
diff --git a/entries/slider.xml b/entries/slider.xml
index 9d4bc7ae..f22bb9b5 100644
--- a/entries/slider.xml
+++ b/entries/slider.xml
@@ -252,7 +252,6 @@ $( "input" ).slider();
 			</desc>
 			<type name="Boolean" />
 		</option>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-mini.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-theme.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="trackTheme" default="null, inherited from parent" example-value='"a"'>
diff --git a/entries/textinput.xml b/entries/textinput.xml
index 6126d2b3..bb1e2685 100644
--- a/entries/textinput.xml
+++ b/entries/textinput.xml
@@ -230,7 +230,6 @@ $( ".mySearchInput" ).textinput();
 		<xi:include href="../includes/widget-option-defaults.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-disabled.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-enhanced.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
-		<xi:include href="../includes/widget-option-initSelector.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<xi:include href="../includes/widget-option-mini.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="preventFocusZoom" default="true on iOS platforms" example-value="true">
 			<desc>Attempts to prevent the device from focusing in on the input element when the element receives the focus.
diff --git a/includes/widget-option-initSelector.xml b/includes/widget-option-initSelector.xml
deleted file mode 100644
index 0a6243cb..00000000
--- a/includes/widget-option-initSelector.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-<?xml version="1.0"?>
-<option name="initSelector" default="See below" deprecated="1.4.0">
-	<desc>
-		<p>The default <code>initSelector</code> for the <placeholder name="name" /> widget is:</p>
-<pre><code>
-"<placeholder name="init-selector"/>"
-</code></pre>
-		<div class="warning">
-			<p><strong>Note:</strong> This option is deprecated in 1.4.0 and will be removed in 1.5.0.<br />
-			As of jQuery Mobile 1.4.0, the <code>initSelector</code> is no longer a widget option. Instead, it is declared directly on the widget prototype. Thus, you may specify a custom value by handling the <code>mobileinit</code> event and overwriting the <code>initSelector</code> on the prototype:</p>
-<pre><code>
-$( document ).on( "mobileinit", function() {
-	$.mobile.<placeholder name="name"/>.prototype.initSelector = "div.custom";
-});
-</code></pre>
-		</div>
-		<p><strong>Note:</strong> Remember to attach the <code>mobileinit</code> handler after you have loaded jQuery, but before you load jQuery Mobile, because the event is triggered as part of jQuery Mobile's loading process.</p>
-		<p>The value of this option is a jQuery selector string. The framework selects elements based on the value of this option and instantiates <placeholder name="name" /> widgets on each of the resulting list of elements.</p>
-	</desc>
-	<type name="Selector" />
-</option>
diff --git a/pages/data-attribute.html b/pages/data-attribute.html
index 79a32bfd..3c53964f 100644
--- a/pages/data-attribute.html
+++ b/pages/data-attribute.html
@@ -25,10 +25,6 @@ <h2><a href="../button/">Button</a></h2>
 		<th>data-iconpos</th>
 		<td><strong>left</strong> | right | top | bottom | notext</td>
 	</tr>
-	<tr>
-		<th>data-iconshadow</th>
-		<td>true | <strong>false</strong> <span class="warning">Deprecated as of 1.4.0 and will be removed in 1.5.0.</span></td>
-	</tr>
 	<tr>
 		<th>data-inline</th>
 		<td>true | <strong>false</strong></td>
@@ -144,17 +140,6 @@ <h2><a href="../collapsibleset/">Collapsible set</a></h2>
 </table>
 <p></p>
 
-<h2>Content</h2>
-<p class="warning"><strong>Note:</strong> Deprecated as of 1.4.0 and will be removed in 1.5.0.</p>
-<p>Container with <code>data-role="content"</code></p>
-<table class="column-headers">
-	<tr>
-		<th>data-theme</th>
-		<td>swatch letter (a-z)</td>
-	</tr>
-</table>
-<p></p>
-
 <h2><a href="../controlgroup/">Controlgroup</a></h2>
 <p>DIV or FIELDSET container with <code>data-role="controlgroup"</code>. Visually integrate multiple button-styled elements.</p>
 <table class="column-headers">
@@ -227,10 +212,6 @@ <h2><a href="global-config">Enhancement</a></h2>
 
 <p>Any link or form element inside <code>data-ajax="false"</code> containers will be ignored by the framework's navigation functionality when <code>$.mobile.ignoreContentEnabled</code> is set to true.</p>
 
-<h2>Field container</h2>
-<p>Container with <code>data-role="fieldcontain"</code> wrapped around label/form element pair</p>
-<p class="warning"><strong>Note:</strong> <code>data-role="fieldcontain"</code> is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0. Add class <code>ui-field-contain</code> instead.</p>
-
 <h2><a href="../flipswitch/">Flip toggle switch</a></h2>
 <p>Select with <code>data-role="slider"</code> and two <code style="font-weight:normal;">option</code> element</p>
 <table class="column-headers">
@@ -300,10 +281,6 @@ <h2><a href="../listview/">Listview</a></h2>
 		<th>data-autodividers</th>
 		<td>true | <strong>false</strong></td>
 	</tr>
-	<tr>
-		<th>data-count-theme</th>
-		<td>swatch letter (a-z) - Default "null", inherited from parent <span class="warning">Deprecated as of 1.4.0 and will be removed in 1.5.0.</span></td>
-	</tr>
 	<tr>
 		<th>data-divider-theme</th>
 		<td>swatch letter (a-z) - Default "null", inherited from parent</td>
diff --git a/pages/global-config.html b/pages/global-config.html
index 7db7f461..34b27bc4 100644
--- a/pages/global-config.html
+++ b/pages/global-config.html
@@ -58,12 +58,6 @@ <h2>Configurable options</h2>
 		<p>The following defaults are configurable via the <code>$.mobile</code> object:</p>
 
 <dl>
-	<dt id="activeBtnClass"><code>activeBtnClass</code> <em>string</em>, default: "ui-btn-active"</dt>
-	<dd>The CSS class used for "active" button state.<div class="warning"><strong>Deprecated</strong> in 1.4 and will be removed in 1.5. The class "ui-btn-active" will continue to be applied to elements as before.</div></dd>
-	<br />
-	<dt id="activePageClass"><code>activePageClass</code> <em>string</em>, default: "ui-page-active"</dt>
-	<dd>The CSS class used for the page currently in view or in a transition.<div class="warning"><strong>Deprecated</strong> in 1.4 and will be removed in 1.5. The class "ui-page-active" will continue to be applied to elements as before.</div></dd>
-	<br />
 	<dt id="ajaxEnabled"><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 ordinary HTTP requests.</dd>
 	<br />
@@ -72,23 +66,6 @@ <h2>Configurable options</h2>
 	<br />
 	<dt id="autoInitializePage"><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, the page will not initialize and will be visually hidden until <code>$.mobile.initializePage</code> is manually called.</dd>
-	<br />
-	<dt id="buttonMarkup.hoverDelay"><code>buttonMarkup.hoverDelay</code> <em>integer</em>, default: 200</dt>
-	<dd>Set the delay for touch devices to add the hover and down classes on touch interactions for buttons throughout the framework. Reducing the delay here results in a more responsive feeling ui, but will often result in the downstate being applied during page scrolling.
-	<div class="warning"><strong>Deprecated</strong> in 1.4 - use <code>$.mobile.hoverDelay</code> instead.</dd>
-	<br />
-	<dt id="defaultDialogTransition"><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.
-	<div class="warning"><strong>Deprecated</strong> in 1.4.</div>
-		<p>When using pages styled as dialogs (<code>data-role="page" data-dialog="true"</code>), if you wish for them to have a different transition than regular pages, you must specify the transition on the link that opens them by adding the attribute <code>data-transition="pop"</code> to the link. "pop" is just an example. You may specify any transition you wish, such as "slide", "flip", or "none".</p>
-		<p>Similarly, when calling the <a href="/pagecontainer/">pagecontainer</a>'s <code>change()</code> method, you must also specify the transition explicitly, if you wish it to be different from the <code>$.mobile.defaultPageTransition</code>:
-		<pre><code>
-$( ":mobile-pagecontainer" )
-	.pagecontainer( "change", "dialog.html", { transition: "pop" } );
-</code></pre>
-		</p>
-	</dd>
-$.mobile.defaultDialogTransition is deprecated.
 	<br />
 	<dt id="defaultPageTransition"><code>defaultPageTransition</code> <em>string</em>, default: 'fade'</dt>
 	<dd>Set the default transition for page changes that use Ajax. Note: default changed from 'slide' to 'fade' in 1.1. Set to 'none' for no transitions.</dd>
@@ -128,9 +105,6 @@ <h2>Configurable options</h2>
 	<dt id="dynamicBaseEnabled"><code>dynamicBaseEnabled</code> <em>boolean</em>, default: true</dt>
 	<dd>When this property is set to <code>false</code> the base tag value in browsers that support a dynamic base tag and URL prefixes in browsers that don't <em>won't</em> be updated to reflect where the page was loaded from. This means that resource references that are relative to the page on which they are defined may break. This option is available for web frameworks that operate under a universal base tag value where all links and assets are relative to a single base.</dd>
 	<br />
-	<dt id="focusClass"><code>focusClass</code> <em>string</em>, default: "ui-focus"</dt>
-	<dd>The CSS class used for "active" button state.<div class="warning"><strong>Deprecated</strong> in 1.4 and will be removed in 1.5. The class "ui-focus" will continue to be applied to elements as before.</div></dd>
-	<br />
 	<dt id="getMaxScrollForTransition"><code>getMaxScrollForTransition</code> <em>function</em></dt>
 	<dd>Set a scroll position breakpoint for transitions. If the scroll position is greater than the value returned by this function, transition "none" will be used. The default function returns three times the height of the window.</dd>
     <br />
@@ -152,9 +126,6 @@ <h2>Configurable options</h2>
 	<dt id="maxTransitionWidth"><code>maxTransitionWidth</code> <em>integer, boolean</em>, default: false</dt>
 	<dd>Set a max width for transitions. The option accepts any number representing a pixel width and its default value <code>false</code>. If a number value is set, transition "none" will be used if the window is wider than the specified value.</dd>
     <br />
-	<dt id="minScrollBack"><code>minScrollBack</code> <em>integer</em>, default: 0</dt>
-	<dd>Minimum scroll distance that will be remembered when returning to a page.<div class="warning"><strong>Deprecated</strong> in 1.4 and will be removed in 1.5. Any and all scrolling will be remembered. This matches native behavior. The old default value of 250 has changed to 0 during the deprecation period.</div></dd>
-	<br />
 	<dt id="ns"><code>ns</code> <em>string</em>, default: ""</dt>
 	<dd>The namespace used in data attributes (e.g., data-role). Can be set to any string, 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>If you use data- namespacing, you will need to update/override one selector in the theme CSS. The following data selectors should incorporate the namespace you're using:
@@ -176,9 +147,6 @@ <h2>Configurable options</h2>
 	<dt id="pushStateEnabled"><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 recommend disabling this feature if Ajax is disabled or if external links are used extensively.</dd>
 	<br />
-	<dt id="subPageUrlKey"><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 <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.<div class="warning"><strong>Deprecated</strong> in 1.4 and will be removed in 1.5. </div></dd>
-	<br />
 	<dt id="transitionFallbacks.[transition]"><code>transitionFallbacks.[transition]</code> <em>string</em>, default: "fade"</dt>
 	<dd>Set the fallback transition for browsers that don't support 3D transforms for a specific transition type.</dd>