815N/A<div class='intro'>

815N/A <p>{{description}}</p>

815N/A</div>

815N/A

815N/A{{>getting-started}}

815N/A

815N/A<h2>Using Button - Quick Start</h2>

815N/A<h3>Button Widgets</h3>

815N/A```

815N/A// Create some button widgets

815N/AYUI().use('button', function(Y){

815N/A

815N/A // A push button widget

815N/A var button = new Y.Button({

815N/A srcNode: '#myButton'

815N/A });

815N/A

815N/A // A toggle button widget

815N/A var toggleButton = new Y.ToggleButton({

815N/A srcNode: '#myToggleButton'

815N/A });

815N/A

815N/A});

815N/A```

815N/A

815N/A<h3>Node Plugin</h3>

815N/A```

815N/A// If you want something a little more light-weight than a widget...

815N/AYUI().use('button-plugin', function(Y){

815N/A

815N/A var button = new Y.Plugin.Button.createNode("#testButton", {

815N/A label: "I'm a disabled button",

815N/A disabled: true

815N/A });

815N/A

815N/A});

815N/A```

815N/A<h3>Button Groups</h3>

815N/A```

815N/A// And if you want to manage a group of buttons

815N/AYUI().use('button-group', function(Y){

815N/A

815N/A var buttonGroup = new Y.ButtonGroup({

815N/A srcNode: '#container' // Should contain <button> children

815N/A });

815N/A

815N/A});

815N/A```

815N/A

815N/A

815N/A

815N/A<h2>Modules</h2>

815N/A<p>YUI's Button component introduces 5 modules:</p>

815N/A<ul>

815N/A <li><a href="#cssbutton">`cssbutton`</a> - Includes various `yui3-button` styles to provide a normalized CSS base for buttons.</li>

815N/A <li><a href="#button">`button`</a> - Exports the `Y.Button` &amp; `Y.ToggleButton` widgets.</li>

815N/A <li><a href="#buttongroup">`button-group`</a> - Exports the `Y.ButtonGroup` widget.</li>

815N/A <li><a href="#buttonplugin">`button-plugin`</a> - Exports the `Y.Plugin.Button.createNode` factory.</li>

815N/A <li>`button-core` - Exports `Y.ButtonCore`, a base used by all other Button component modules.</li>

815N/A</ul>

815N/A

815N/A

815N/A<h3>Which one to use?</h3>

815N/A<ul>

815N/A <li>`use('cssbutton')` if you only want a CSS stylesheet to enhance button(-like) nodes</li>

815N/A <li>`use('button-plugin')` if you only need to enhance a DOM node with button functionality</li>

815N/A <li>`use('button')` if you want a button widget</li>

815N/A <li>`use('button-group')` if you want a widget to manage a group of buttons</li>

815N/A <li>`button-core` is not intended to be used stand-alone</li>

815N/A</ul>

815N/A

815N/A<div id="cssbutton">

815N/A <h3>use('cssbutton')</h3>

815N/A <p>YUI's Button component was designed with the idea in mind that sometimes you may only want button styles, without the need for any JavaScript functionality. Instead of `use('button', ...)`, you can just include the `cssbutton` module. This can be done dynamically with `use('cssbutton')`, or statically with a `link` tag.</p>

815N/A```

815N/A<link rel="stylesheet" href="http://yui.yahooapis.com/{{yuiVersion}}/build/cssbutton/cssbutton.css">

815N/A```

815N/A

815N/A <p>Loading this stylesheet will include the following classes:</p>

815N/A <ul>

815N/A <li>yui3-button</li>

815N/A <li>yui3-button-disabled</li>

815N/A <li>yui3-button-hover, yui3-button:hover</li>

815N/A <li>yui3-button-active, yui3-button:active</li>

815N/A <li>yui3-button-primary, yui3-button-selected</li>

815N/A </ul>

815N/A

815N/A <p>These styles are designed to progressively enhance. In legacy browsers, you'll get styles that appear as basic buttons, and in new browsers you'll get buttons using modern styles. cssbutton is intended to provide a base and be overridable with custom styles. Such as `background-color`.</p>

815N/A

815N/A <h5>Background Color</h5>

815N/A <p>A feature of cssbutton is that it uses transparent gradients to create a colored effect. So if you would like a button that has a light to dark red gradient, you do not need to specify all the styles for proper cross-browser gradients, you only need to specify a single `background-color` style to your buttons.</p>

815N/A</div>

815N/A

815N/A

815N/A<div id="buttonplugin">

815N/A <h3>use('button-core')</h3>

815N/A <p>This module serves as the foundation for all Button component JavaScript modules and exports `Y.ButtonCore`. While you can use it stand-alone if you like, it is typically a foundational building block for all other Button classes.</p>

815N/A</div>

815N/A

815N/A

815N/A<div id="buttonplugin">

815N/A <h3>use('button-plugin')</h3>

815N/A <p>This module exports the `Y.Plugin.Node.createNode` factory, which simplifies the process of plugging nodes with `Y.ButtonCore`.</p>

815N/A</div>

815N/A

815N/A

815N/A<div id="button">

815N/A <h3>use('button')</h3>

815N/A

815N/A <h4>Y.Button</h4>

815N/A <p>`Y.Button` combines `Y.ButtonCore` with `Y.Widget`, to give you basic button functionality, but with the benefits of having a <a href='/yui/docs/widget/'>Widget</a> instance. This can be used as a building block for different types of advanced buttons.</p>

815N/A

815N/A <h4>Y.ToggleButton</h4>

815N/A <p>`Y.ToggleButton` does everything that `Y.Button` does (by extending it), and adds the concept of a selected state, which is referred to as either 'pressed' or 'checked', depending on the `type` attribute of the instance. This distinction is made for proper ARIA support.</p>

815N/A

815N/A <h4>Benefits</h4>

815N/A

815N/A <p>So what do you get from `Y.Button`/`Y.ToggleButton` over just creating or plugging a `<button>` node?</p>

815N/A

815N/A <ul>

815N/A <li><strong>Accessibility</strong> - Your buttons automatically create and manage their own ARIA <a href='http://www.w3.org/TR/wai-aria/states_and_properties'>states</a> &amp; <a href='http://www.w3.org/TR/wai-aria/roles'>roles</a>. This includes states like `aria-pressed` &amp; `aria-checked`, also appropriate roles like `button`, `checked`, `radio`, etc...</li>

815N/A <li><strong>State management</strong> - Instances automatically apply classes, such as `yui3-button-selected` and `yui3-button-disabled` which are useful for styling purposes. Also, `Y.ToggleButton` will fire a 'pressedChange' or 'checkedChange' event (depending on `type`) when the button's state changes from selected to unselected, or vice-versa. This event eliminates the typical case of listening for all 'click' events and then verifying a state changed actually did occur.</li>

815N/A </ul>

815N/A</div>

815N/A

815N/A

815N/A<div id="buttongroup">

815N/A <h3>use('button-group')</h3>

815N/A <p>`Y.ButtonGroup` is a constructor that is used to generate widgets containing a group of buttons. To avoid widgets inside of widgets, this class is built on top of `Y.ButtonCore`, not `Y.Button`</p>

815N/A</div>

815N/A

815N/A

815N/A<h2>Reference</h2>

815N/A<p><strong>Note</strong>: This is not an exhaustive list. See the API documentation for a complete listing.</p>

815N/A<h3>Attributes</h3>

815N/A<h4>Y.ButtonCore</h4>

815N/A<table>

815N/A <thead>

<tr>

<th>Attribute</th>

<th>Data type</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td>label</td>

<td>string</td>

<td>

Sets the button's `innerHTML` or `value` attribute depending on node type

</td>

</tr>

<tr>

<td>disabled</td>

<td>boolean</td>

<td>

Sets the button's disabled state to true/false

</td>

</tr>

</tbody>

</table>

<h4>Node Plugin</h4>

<p>Inherited from `Y.ButtonCore`</p>

<h4>Y.Button</h4>

<p>Identical to `Y.ButtonCore`</p>

<h4>Y.ToggleButton</h4>

<p>In addition to the inherited `Y.Button` attributes...</p>

<table>

<thead>

<tr>

<th>Attribute</th>

<th>Data type</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td>type</td>

<td>string</td>

<td>

<p>Sets the type of a toggleable button.</p>

<p>Possible values:

<ul>

<li>'toggle' (default)</li>

<li>'checkbox' </li>

</ul>

</p>

<p>The difference is that a 'toggle' button will use <a href='http://www.w3.org/TR/wai-aria/states_and_properties#aria-pressed'>aria-pressed</a>, and a 'checkbox' button will use <a href='http://www.w3.org/TR/wai-aria/states_and_properties#aria-checked'>aria-checked</a>.</p> </td>

</tr>

</tbody>

</table>

<h4>Y.ButtonGroup</h4>

<p>In addition to the inherited `Y.ButtonCore` attributes...</p>

<table>

<thead>

<tr>

<th>Attribute</th>

<th>Data type</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td>type</td>

<td>string</td>

<td>

<p>Sets the type of button group</p>

<p>Possible values:

<ul>

<li>'push' (default) - No buttons have a selectable state</li>

<li>'radio' - Only one button is selectable at a time</li>

<li>'checkbox' - Multiple buttons can be selected at a time</li>

</ul>

</p>

</td>

</tr>

</tbody>

</table>

<h3>Change Events</h3>

<h4>Y.ButtonCore</h4>

<table>

<thead>

<tr>

<th>Event</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td>labelChange</td>

<td>

Fires to inform the subscriber that the button's label is about to be, or has been updated.

</td>

</tr>

<tr>

<td>disabledChange</td>

<td>

Fires to notify the subscriber the disabled state is about to be, or has been updated.

</td>

</tr>

</tbody>

</table>

<h4>Node Plugin</h4>

<p>Inherited from `Y.ButtonCore`</p>

<h4>Y.Button</h4>

<p>Identical to `Y.ButtonCore`</p>

<h4>Y.ToggleButton</h4>

<p>In addition to the inherited `Y.Button` events...</p>

<table>

<thead>

<tr>

<th>Event</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td>pressedChange</td>

<td>

Fires for toggle buttons to notify the subscriber the selected state is about to be, or has been updated.

</td>

</tr>

<tr>

<td>checkedChange</td>

<td>

Identical to `"pressedChange"`, but only applicable for buttons with a configuration attribute `"type: 'checkbox'"`.

</td>

</tr>

</tbody>

</table>

<h4>Y.ButtonGroup</h4>

<p>In addition to the inherited `Y.ButtonCore` events...</p>

<table>

<thead>

<tr>

<th>Event</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td>selectionChange</td>

<td>

Fires when a button within the group is either selected or unselected. The event payload contains a reference `'originEvent'` to the original event, which can be used to obtain the target button.

</td>

</tr>

</tbody>

</table>

<p>

Note:

<br>`.on('eventName', fn)` will fire <strong>before</strong> the attribute &amp; UI are updated.

<br>`.after('eventName', fn)` will fire <strong>after</strong> the attribute &amp; UI are updated.

</p>