Skip to content
Closed
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
124 commits
Select commit Hold shift + click to select a range
a8c69c9
deprecate pageinit
johnbender Apr 16, 2013
e8dda56
Popup: Document option "arrow" added by the popup arrow extension.
Jul 30, 2013
69ead2b
entries and resources: Removing trailing whitespace.
Aug 17, 2013
3dc49d8
resources: Moving to jQM 1.4.0-alpha.2
Aug 17, 2013
a2098ff
Button: Updating for 1.4.0.
Aug 17, 2013
0064bb4
entries2html.xsl: Updating to 1.4.0-alpha.2 and removing script that …
Aug 17, 2013
809b378
entries: <code> blah</code> becomes <code>blah</code>.
Aug 17, 2013
721a502
Button: Documenting new options.
Aug 18, 2013
8e37e5b
Button: Re-organizing <h*> tags so they make more sense.
Aug 26, 2013
3ed9d6a
Checkboxradio: Documenting new options.
Aug 26, 2013
6bd8eaa
Collapsible set: Updating to reflect removal of the dash from "collap…
Aug 28, 2013
1699706
Collapsible set: Documenting new options.
Aug 28, 2013
6f7acc9
Collapsible set: Adding documentation about pre-rendering.
Aug 29, 2013
72f49d5
Collapsible: Updating for 1.4.0.
Aug 30, 2013
6b8c467
Textinput: Document new refresh() method.
Aug 30, 2013
a1ef950
Checkbox: Forgot to add example illustrating pre-rendering.
Aug 30, 2013
404f08e
Fixing theme swatch examples: b is the new dark swatch (replacing a) …
Sep 2, 2013
f776de2
Adding and referencing standard widget includes and adding missing in…
Sep 2, 2013
5381cde
Updated documentation about using custom icons. Fixes #143.
jaspermdegroot Sep 3, 2013
55b7264
Button: Move buttonMarkup into its own entry. Fixes #85.
Sep 2, 2013
f92f222
Button: Making the options portion more systematic.
Sep 4, 2013
fc0e05e
Checkboxradio: Touch up some options.
Sep 5, 2013
933e757
Giving all widget the initSelector option.
Sep 5, 2013
db9766c
Popup: Adding popup arrow documentation and example.
Sep 5, 2013
e12aab2
Rangeslider: Updating.
Sep 6, 2013
3f81c0c
Theme option: Creating include and applying it wherever its definitio…
Sep 6, 2013
d8678c4
15px padding for ui-content became 1em.
jaspermdegroot Sep 8, 2013
d53b491
Removed nested listviews.
jaspermdegroot Sep 8, 2013
cae467e
Button: Using <placeholder name="name"/> instead of button in a bunch…
Sep 8, 2013
fb9e7be
Popup: Documenting the two different types of the "arrow" option sepa…
Sep 8, 2013
ab58c46
Option enhanced: Factoring out into includes/widget-option-enhanced.xml
Sep 8, 2013
d692f0f
Collapsibleset: Modify blurb about initSelector option.
Sep 8, 2013
efe379f
Adding include for option initSelector.
Sep 8, 2013
e141bed
button and buttonMarkup: Marking option iconshadow as deprecated.
Sep 8, 2013
be8efdd
Filterable: New entry.
Sep 8, 2013
91a289f
Select: Deprecating option iconshadow.
Sep 8, 2013
4c499e4
Filterable: Removing popup example from the end of the file.
Sep 9, 2013
3cdb31f
Toolbar: Collecting header and footer into one place.
Sep 9, 2013
710ae1b
Toolbar: Minor fixes
Sep 9, 2013
6e5400b
Fixed toolbar: Moving into toolbar.
Sep 9, 2013
6e0d4d7
toolbar: Documenting options.
Sep 10, 2013
5a5772e
Toolbar: Documenting methods.
Sep 10, 2013
717eb6f
Dialog: Adding deprecation notice.
Sep 10, 2013
e28d4e3
Button: Updating options "inline" and "mini".
Sep 10, 2013
d947ae7
Textinput: Updating.
Sep 10, 2013
14368ec
Option mini: New include and corresponding references.
Sep 10, 2013
3f10519
Panel: Updating.
Sep 11, 2013
f0bb0e5
Custom select: Deprecating the behaviour whereby <option value="">Des…
Sep 11, 2013
275b0f9
Panel: Re-arranging options.
Sep 13, 2013
2414ad4
Button, select, textinput, and option "mini": Fixing XML tag mismatch…
Sep 15, 2013
73d8122
Loader: Removing references to deprecated items.
Sep 16, 2013
681af1f
You can use data-collapsed-icon="false" to have a collapsible without…
jaspermdegroot Sep 16, 2013
8ed1230
Pagecontainer: New entry.
Sep 17, 2013
e5629c0
Pageload and pagebeforeload: Deprecating and pointing to correspondin…
Sep 17, 2013
e5c0b6c
Collapsible: Documenting that collapsedIcon can also be a boolean (fa…
Sep 17, 2013
e654cbc
Pagecontainer: Moving event pageloadfailed into event pagecontainerlo…
Sep 17, 2013
53f979b
Pagecontainer: Moving event pagechangefailed into event pagecontainer…
Sep 17, 2013
f17aca6
Pagecontainer: Moving event pagehide into event pagecontainerhide.
Sep 17, 2013
7919def
Pagecontainer: Moving event pageshow into event pagecontainershow, an…
Sep 18, 2013
9688e5a
Page: add option keepNative and mark it as deprecated.
Sep 18, 2013
a980192
Pagecontainer: Documenting events beforetransition and transition.
Sep 18, 2013
2a3c9be
Pagecontainer: Move methods $.mobile.changePage and $.mobile.loadPage…
Sep 19, 2013
6f7bd48
changePage and loadPage: Cleaning up description.
Sep 19, 2013
1612057
buttonMarkup: Added deprecation warning.
Sep 19, 2013
2dbfbcd
Slider and range slider: Added deprecation warning
Sep 19, 2013
81bd284
Classes: New entry for documenting CSS classes.
Sep 23, 2013
9832e6c
Classes: Changing the wording for inset.
Sep 23, 2013
c56aef8
Examples: Moving from old-style git URL to new-style alpha.2 URL.
Sep 23, 2013
364f81d
Button: Marking style options as deprecated.
Sep 23, 2013
b1571ea
Checkboxradio: Deprecating style options.
Sep 23, 2013
56f8a47
Controlgroup: Deprecating style options.
Sep 23, 2013
5f60a86
Page: Deprecating style options.
Sep 23, 2013
c95a57a
Button: Correcting blurb about shadow.
Sep 23, 2013
b462142
Popup: Deprecating style options.
Sep 23, 2013
2d8fe77
Controlgroup: Correcting blurb about mini.
Sep 23, 2013
c10d855
Textinput: Deprecating style options.
Sep 23, 2013
008cd3d
Toolbar: Deprecating style options.
Sep 23, 2013
0615cd5
Table: Deprecated table-stroke and table-stripe classes.
jaspermdegroot Sep 23, 2013
f59ffeb
Revert style option deprecations.
Sep 24, 2013
697d695
Theme: Add entry explaining the concepts. Fixes #153 - Document that …
Sep 24, 2013
96b770b
Updated 1.4 API docs intro page.
jaspermdegroot Sep 24, 2013
08a7d31
Resources: Moving to 1.4.0-beta.1
Sep 24, 2013
90d5a9a
Resources: Popup: Remove source files and references to source files …
Sep 24, 2013
64d4b02
Controlgroup: Updating examples to not use data-role="button"
Sep 30, 2013
0b8c75f
Panel: Updated responsive panel CSS example.
jaspermdegroot Sep 30, 2013
aaacff3
global-config: Add deprecation warning to buttonMarkup related option.
Oct 2, 2013
5b40f6f
global-config: Remove global configuration options related to the loa…
Oct 2, 2013
c3bcde6
buttonMarkup: Added migration examples.
Oct 3, 2013
86ab7bd
buttonMarkup: Added blurb saying we do not recommend that people mix …
Oct 3, 2013
62007d5
Popup: Adding pre-rendered example.
Oct 3, 2013
39878ba
Checkboxradio: Updated example of pre-rendered checkbox to reflect ne…
Oct 3, 2013
d0a8f12
Textinput: Add section about and example of pre-rendered widget.
Oct 3, 2013
10bc8f9
Toolbar: Add example illustrating dynamic fixed toolbar injection.
Oct 4, 2013
d866229
Renamed Toolbars to Toolbar Widget
jaspermdegroot Oct 4, 2013
2713858
Data- attr reference: Updated field container section.
jaspermdegroot Oct 4, 2013
b59d677
Added toolbar section to data- attr reference. Addresses #82
jaspermdegroot Oct 4, 2013
0767ea3
Data- attr reference: Updated "Page" section.
jaspermdegroot Oct 4, 2013
4a59692
Fixed broken links in data- attr reference.
jaspermdegroot Oct 4, 2013
c2c8171
Data- attr reference: Moved fixed toobar to toolbar section and link …
jaspermdegroot Oct 4, 2013
da4f50a
Page: Removed note about IE7 because it's a C-grade browser as from 1.4.
jaspermdegroot Oct 4, 2013
b116197
Toolbar: Updated info about auto enhancement of buttons being depreca…
jaspermdegroot Oct 4, 2013
1003f11
Toolbar: Auto adding of ui-btn-left/right has been deprecated.
jaspermdegroot Oct 4, 2013
fd13972
Data- attr reference: Use the widget name as section heading.
jaspermdegroot Oct 4, 2013
18b9a8e
Renamed select to selectmenu, the actual widget name.
jaspermdegroot Oct 4, 2013
c345220
Toolbar: Added info about setting a theme being required for external…
jaspermdegroot Oct 4, 2013
8b9518d
Navbar: Added not about ui-state-persist doesn't work with external t…
jaspermdegroot Oct 6, 2013
1f48b76
Changed Header, Footer, Fixedtoolbar description: refer to Toolbar Wi…
jaspermdegroot Oct 6, 2013
3b1f100
Updated controlgroup documentation.
jaspermdegroot Oct 6, 2013
f90d071
Updated to class ui-field-contain and added note about data-role="fie…
jaspermdegroot Oct 6, 2013
e337591
Re-wording pre-rendered intro blurb.
Oct 8, 2013
4328157
Flipswitch: Adding entry.
Oct 8, 2013
4b56392
Flipswitch: Forgot to mark data-corners="false" in pre-rendered example.
Oct 8, 2013
8cfdbcb
Pre-rendered markup: Adding blurb about having to add the attribute d…
Oct 8, 2013
1d1d133
Pre-rendered widgets: Factoring out common text.
Oct 8, 2013
5f00b49
Column toggle table: Adding documentation about pre-rendered content.
Oct 9, 2013
f8007e8
Updating core version to 1.10.2 and jQuery Mobile version to git.
Oct 9, 2013
25cb9b7
set-lib-versions.sh: Script to replace core and mobile version in ent…
Oct 9, 2013
8a0b175
set-lib-versions.sh: Added blurb about what it does.
Oct 13, 2013
5527668
Global config: Deprecating defaultDialogTransition, and adding IDs to…
Oct 15, 2013
c6a6997
Global config: Removing touchOverflowEnabled, which was deprecated in…
Oct 15, 2013
3ecd9dd
Global config: Expanded on how to give dialog-styled pages a differen…
Oct 16, 2013
31bb217
Global config: Deprecated $.mobile.minScrollBack and $.mobile.subPage…
Oct 16, 2013
7f31270
Categories: Add deprecation notice to the "Widgets" category indicati…
Oct 16, 2013
17488d9
buttonMarkup: Fixed the broken link in buttonMarkup API.
hyunsook Oct 21, 2013
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Button: Updating for 1.4.0.
  • Loading branch information
Gabriel Schulhof committed Aug 17, 2013
commit a2098ffd28b12e362bf5fad4696da5ad7588581e
56 changes: 21 additions & 35 deletions entries/button.xml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
<entry name="buttonMarkup" namespace="fn" type="widget" widgetnamespace="mobile" event-prefix="button">
<entry name="button" type="widget" widgetnamespace="mobile" event-prefix="button">
<title>Button Widget</title>
<desc>Creates a button widget</desc>
<longdesc>
Expand All @@ -16,10 +16,10 @@
<p>Produces this <strong>link-based</strong> button:
<iframe src="/resources/button/example1.html" style="width:100%;height:90px;border:0px"></iframe></p>

<p><strong>Note:</strong> Links styled like buttons have all the same visual options as true form-based buttons below, but there are a few important differences. Link-based buttons aren't part of the <code>button</code> plugin and only just use the underlying <code>buttonMarkup</code> plugin to generate the button styles so the form button methods (enable, disable, refresh) aren't supported. If you need to disable a link-based button (or any element), it's possible to apply the disabled class ui-disabled yourself with JavaScript to achieve the same effect.</p>
<p><strong>Note:</strong> Links styled like buttons have all the same visual options as true form-based buttons below, but there are a few important differences. Link-based buttons aren't part of the <code>button</code> plugin and only just use the underlying <code>buttonMarkup</code> plugin to generate the button styles so the form button methods (enable, disable, refresh) aren't supported. If you need to disable a link-based button (or any element), it's possible to apply the disabled class ui-state-disabled yourself with JavaScript to achieve the same effect.</p>

<pre><code>
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; class=&quot;ui-disabled&quot;&gt;Link button&lt;/a&gt;
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; class=&quot;ui-state-disabled&quot;&gt;Link button&lt;/a&gt;
</code></pre>

<p>Produces this disabled <strong>link-based</strong> button:
Expand All @@ -43,7 +43,7 @@
<p>For ease of styling, the framework automatically converts any <code>button</code> or <code>input</code> element with a <code>type</code> of <code>submit</code>, <code>reset</code>, or <code>button</code> into a custom styled button - there is no need to add the <code> data-role="button"</code> attribute. However, if needed, you can directly call the button plugin on any selector, just like any jQuery plugin:</p>

<pre><code>
$( "[type="submit"]" ).button();
$( "[type='submit']" ).button();
</code></pre>

<p><strong>Button</strong> based button:</p>
Expand Down Expand Up @@ -78,8 +78,7 @@ $( "[type="submit"]" ).button();
<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, the following markup:</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>
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; data-icon=&quot;delete&quot;&gt;Delete&lt;/a&gt;
Expand All @@ -89,21 +88,21 @@ $( "[type="submit"]" ).button();

<h3>Icon set</h3>

<p>The following <code> data-icon</code> attributes can be referenced to create the icons shown below:
<p>The following <code>data-icon</code> attributes can be referenced to create the icons shown below:
<iframe src="/resources/button/example10.html" style="width:100%;height:1840px;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/button/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, the markup:</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>
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; data-icon=&quot;delete&quot; data-iconpos=&quot;right&quot;&gt;Delete&lt;/a&gt;
</code></pre>

<iframe src="/resources/button/example12.html" style="width:100%;height:360px;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>
<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>
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; data-icon=&quot;delete&quot; data-iconpos=&quot;notext&quot;&gt;Delete&lt;/a&gt;
Expand All @@ -117,7 +116,7 @@ $( "[type="submit"]" ).button();
<iframe src="/resources/button/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>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</code> class to specify the icon background source. To maintain visual consistency with the rest of the icons, create a white icon 18x18 pixels saved as a PNG-8 with alpha transparency.</p>
<p>In this example, we're just pointing to a standalone icon image, but you could just as easily use an icon sprite and specify the positioning instead, just like the icon sprite we use in the framework.</p>

Expand Down Expand Up @@ -147,15 +146,13 @@ $( "[type="submit"]" ).button();
<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/button/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>
<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>
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; data-inline=&quot;true&quot;&gt;Cancel&lt;/a&gt;
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; data-inline=&quot;true&quot; data-theme=&quot;b&quot;&gt;Save&lt;/a&gt;
</code></pre>


<iframe src="/resources/button/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>
Expand All @@ -166,7 +163,7 @@ $( "[type="submit"]" ).button();

<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>
<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>
&lt;div data-role=&quot;controlgroup&quot;&gt;
Expand All @@ -189,11 +186,11 @@ $( "[type="submit"]" ).button();

<h2>Theming buttons</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" (black in the default theme) will be automatically assigned the button theme of "a" (charcoal in the default theme). Here are examples of the button theme pairings in the default theme. All buttons have the same HTML markup:
<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/button/example33.html" style="width:100%;height:640px;border:0px"></iframe></p>

<h2>Assigning theme swatches</h2>
<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>
<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>
&lt;a href=&quot;index.html&quot; data-role=&quot;button&quot; data-theme=&quot;a&quot;&gt;Swatch a&lt;/a&gt;
Expand All @@ -209,17 +206,6 @@ $( "[type="submit"]" ).button();
</longdesc>
<added>1.0</added>
<options>
<option name="initSelector" default="button, [type='button'], [type='submit'], [type='reset']">
<desc>This is used to define the selectors (element types, data roles, etc.) that will automatically be initialized as form buttons. To change which elements are initialized, bind this option to the mobileinit event:
<pre><code>
$( document ).on( "mobileinit", function() {
$.mobile.button.prototype.options.initSelector = ".myButtons";
});
</code></pre>
<p><b>Note: This option applies only to form buttons, which are automatically initialized by the framework.</b></p>
</desc>
<type name="CSS selector string" />
</option>
<option name="corners" default="true" example-value="false">
<desc>Applies the theme button border-radius if set to true.
<pre><code>
Expand All @@ -229,7 +215,7 @@ $( "a" ).buttonMarkup({ corners: false });
<iframe src="/resources/button/example40.html" style="width:100%;height:90px;border:0px"></iframe>
</p>
</desc>
<type name="Boolean" />
<type name="Boolean" />
</option>
<option name="icon" default="null" example-value='"star"'>
<desc>Applies an icon from the icon set.
Expand All @@ -240,7 +226,7 @@ $( "a" ).buttonMarkup({ icon: "star" });
<iframe src="/resources/button/example41.html" style="width:100%;height:90px;border:0px"></iframe>
</p>
</desc>
<type name="String" />
<type name="String" />
</option>
<option name="iconpos" default='"left"'>
<desc>Positions the icon in the button. Possible values: left, right, top, bottom, none, notext. The notext value will display an icon-only button with no text feedback.
Expand All @@ -251,7 +237,7 @@ $( "a" ).buttonMarkup({ iconpos: "right" });
<iframe src="/resources/button/example42.html" style="width:100%;height:90px;border:0px"></iframe>
</p>
</desc>
<type name="String" />
<type name="String" />
</option>
<option name="iconshadow" default="true">
<desc>Applies the theme shadow to the button's icon if set to true.
Expand All @@ -262,7 +248,7 @@ $( "a" ).buttonMarkup({ iconshadow: false });
<iframe src="/resources/button/example43.html" style="width:100%;height:90px;border:0px"></iframe>
</p>
</desc>
<type name="Boolean" />
<type name="Boolean" />
</option>
<option name="inline" default="null (false)">
<desc>If set to true, this will make the button act like an inline button so the width is determined by the button's text. By default, this is null (false) so the button is full width, regardless of the feedback content. Possible values: true, false.
Expand All @@ -273,7 +259,7 @@ $( "a" ).buttonMarkup({ inline: true });
<iframe src="/resources/button/example44.html" style="width:100%;height:90px;border:0px"></iframe>
</p>
</desc>
<type name="Boolean" />
<type name="Boolean" />
</option>
<option name="mini" default="null (false)">
<desc>If set to true, this will display a more compact version of the button that uses less vertical height. Possible values: true, false.
Expand All @@ -283,7 +269,7 @@ $( "a" ).buttonMarkup({ mini: true });
<p>This option is also exposed as a data attribute: <code>data-mini="true"</code>.
<iframe src="/resources/button/example45.html" style="width:100%;height:90px;border:0px"></iframe></p>
</desc>
<type name="Boolean" />
<type name="Boolean" />
</option>
<option name="shadow" default="true">
<desc>Applies the drop shadow style to the button if set to true.
Expand All @@ -294,10 +280,10 @@ $( "a" ).buttonMarkup({ shadow: false });
<iframe src="/resources/button/example46.html" style="width:100%;height:90px;border:0px"></iframe>
</p>
</desc>
<type name="Boolean" />
<type name="Boolean" />
</option>
<option name="theme" default="null, inherited from parent">
<desc><p>Sets the color scheme (swatch) for all instances of this widget. It accepts a single letter from a-z that maps to one of the swatches included in your theme. By default, it will inherit the same swatch color as its parent container if not explicitly set. </p>
<desc><p>Sets the color scheme (swatch) for all instances of this widget. It accepts a single letter from a-z that maps to one of the swatches included in your theme. By default, it will inherit the same swatch color as its parent container if not explicitly set.</p>
<pre><code>
$( "a" ).buttonMarkup({ theme: "a" });
</code></pre>
Expand Down
2 changes: 1 addition & 1 deletion resources/button/example2.html
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
<body>
<div data-role="page" style="max-height:90px; min-height:90px;">
<div data-role="content" >
<a href="index.html" data-role="button" class="ui-disabled">Link button</a>
<a href="index.html" data-role="button" class="ui-state-disabled">Link button</a>
</div>
</div>
</body>
Expand Down