Merge branch 'master' into selectmenu

Conflicts:
	entries2html.xsl

Author: fnagel

README.md

@@ -11,7 +11,4 @@ The `xmllint` and `xsltproc` utilities need to be in your path. If you are on Wi
 
 ### Build
 
-1. `npm install`
-2. `cp config-sample.json config.json`
-3. Edit config.json per https://github.com/scottgonzalez/grunt-wordpress#config
-4. `grunt`
+To build and deploy your changes for previewing in a [`jquery-wp-content`](https://github.com/jquery/jquery-wp-content) instance, follow the [workflow instructions](http://contribute.jquery.org/web-sites/#workflow) from our documentation on [contributing to jQuery Foundation web sites](http://contribute.jquery.org/web-sites/).

categories.xml

@@ -34,7 +34,7 @@
 	</category>
 	<category name="Effects Core" slug="effects-core">
 		<desc><![CDATA[
-			<p>Functionality provided by jquery.ui.effect.js.</p>
+			<p>Functionality provided by jquery.ui.effect.js. In addition to the methods listed below, jquery.ui.effect.js also includes several <a href="/easings/">easings</a>.</p>
 		]]></desc>
 	</category>
 	<category name="All" slug="all"/>

entries/accordion.xml

@@ -32,6 +32,13 @@
 		<ul>
 			<li>CTRL+UP: Move focus to associated header.</li>
 		</ul>
+
+		<h3>Dependencies</h3>
+		<ul>
+			<li><a href="/category/ui-core/">UI Core</a></li>
+			<li><a href="/jQuery.widget/">Widget Factory</a></li>
+			<li><a href="/category/effects-core/">Effects Core</a> (optional; for use with the <a href="#option-animate"><code>animate</code></a> option)</li>
+		</ul>
 	</longdesc>
 	<note id="functional-css"/>
 	<added>1.0</added>

entries/autocomplete.xml

@@ -7,7 +7,7 @@
 
 		<p>This can be used to choose previously selected values, such as entering tags for articles or entering email addresses from an address book. Autocomplete can also be used to populate associated information, such as entering a city name and getting the zip code.</p>
 
-		<p>You can pull data in from a local or remote source: Local is good for small data sets, e.g., an address book with 50 entries; remote is necessary for big data sets, such as a database with hundreds or millions of entries to select from. To find out more about customizing the data soure, see the documentation for the <a href="#option-source"><code>source</code></a> option.</p>
+		<p>You can pull data in from a local or remote source: Local is good for small data sets, e.g., an address book with 50 entries; remote is necessary for big data sets, such as a database with hundreds or millions of entries to select from. To find out more about customizing the data source, see the documentation for the <a href="#option-source"><code>source</code></a> option.</p>
 
 		<h3>Keyboard interaction</h3>
 
@@ -25,12 +25,21 @@
 		<ul>
 			<li>UP/DOWN - Open the menu, if the <a href="#option-minLength"><code>minLength</code></a> has been met.</li>
 		</ul>
+
+		<h3>Dependencies</h3>
+		<ul>
+			<li><a href="/category/ui-core/">UI Core</a></li>
+			<li><a href="/jQuery.widget/">Widget Factory</a></li>
+			<li><a href="/position/">Position</a></li>
+			<li><a href="/menu/">Menu</a></li>
+		</ul>
 	</longdesc>
 	<note id="functional-css"/>
+	<note id="native-change-warning"/>
 	<added>1.8</added>
 	<options>
-		<option name="appendTo" type="Selector" default='"body"' example-value='"#someElem"'>
-			<desc>Which element the menu should be appended to. Override this when the autocomplete is inside a <code>position: fixed</code> element. Otherwise the popup menu would still scroll with the page.</desc>
+		<option name="appendTo" type="Selector" default="null" example-value='"#someElem"'>
+			<desc>Which element the menu should be appended to. When the value is <code>null</code>, the parents of the input field will be checked for a class of <code>ui-front</code>. If an element with the <code>ui-front</code> class is found, the menu will be appended to that element. Regardless of the value, if no element is found, the menu will be appended to the body.</desc>
 		</option>
 		<option name="autoFocus" type="Boolean" default="false" example-value="true">
 			<desc>If set to <code>true</code> the first item will automatically be focused when the menu is shown.</desc>
@@ -153,7 +162,7 @@
 				<desc></desc>
 			</argument>
 		</method>
-		<method name="widget">
+		<method name="widget" return="jQuery">
 			<desc>Returns a <code>jQuery</code> object containing the menu element. Although the menu items are constantly created and destroyed, the menu element itself is created during initialization and is constantly reused.</desc>
 		</method>
 	</methods>

entries/button.xml

@@ -1,15 +1,21 @@
 <?xml version="1.0"?>
 <entry name="button" type="widget" widget-element="element visually representing the button">
 	<title>Button Widget</title>
-	<desc>Themable buttons and button sets.</desc>
+	<desc>Themeable buttons and button sets.</desc>
 	<longdesc>
-		<p>Button enhances standard form elements like buttons, inputs and anchors to themable buttons with appropiate hover and active styles.</p>
+		<p>Button enhances standard form elements like buttons, inputs and anchors to themeable buttons with appropriate hover and active styles.</p>
 
-		<p>In addition to basic push buttons, radio buttons and checkboxes (inputs of type radio and checkbox) can be converted to buttons. Their associated label is styled to appear as the button, while the underlying input is updated on click. For the association to work properly, give the input an <code>id</code> attribute, and refer to that in the label's <code>for</code> attribute. Don't nest the input inside the label, as that <a href="http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-form-control-labeling/">causes accessbility problems</a>.</p>
+		<p>In addition to basic push buttons, radio buttons and checkboxes (inputs of type radio and checkbox) can be converted to buttons. Their associated label is styled to appear as the button, while the underlying input is updated on click. For the association to work properly, give the input an <code>id</code> attribute, and refer to that in the label's <code>for</code> attribute. Don't nest the input inside the label, as that <a href="http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-form-control-labeling/">causes accessibility problems</a>.</p>
 
 		<p>In order to group radio buttons, Button also provides an additional widget, called Buttonset. Buttonset is used by selecting a container element (which contains the radio buttons) and calling <code>.buttonset()</code>. Buttonset will also provide visual grouping, and therefore should be used whenever you have a group of buttons. It works by selecting all descendants and applying <code>.button()</code> to them. You can enable and disable a button set, which will enable and disable all contained buttons. Destroying a button set also calls each button's <code>destroy</code> method.</p>
 
 		<p>When using an input of type button, submit or reset, support is limited to plain text labels with no icons.</p>
+
+		<h3>Dependencies</h3>
+		<ul>
+			<li><a href="/category/ui-core/">UI Core</a></li>
+			<li><a href="/jQuery.widget/">Widget Factory</a></li>
+		</ul>
 	</longdesc>
 	<note id="functional-css"/>
 	<added>1.8</added>