Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Text Input doesn't use ui-disabled class if disabled attribute is set in markup #4636

Closed
patrick-wolf opened this Issue · 2 comments

2 participants

@patrick-wolf

For a form element of type "Text Input" the ui-disabled class isn't set during initialization of the widget if the "disabled" attribute is already set in the markup.

See http://jquerymobile.com/test/docs/forms/docs-forms.html (Disabling form elements)

This is inconsistent with the behavior of the textinput API, because

$( "#foo" ).textinput( "disable" );

will disable the text field AND set the ui-disabled class.

@jaspermdegroot
Collaborator

@patrickwolfat

Thanks for reporting the issues with the disabled textinput. In my comment at #4637 I explained the cause.

@patrick-wolf

Thanks for providing a fix that fast!

@jaspermdegroot jaspermdegroot closed this issue from a commit
@jaspermdegroot jaspermdegroot Textinput: added conditional call to disable() to the create function…
… to make sure disabled elements get class ui-disabled. Fixes #4636 and #4637 - Text Input doesn't use ui-disabled class if disabled attribute is set in markup. [1.1.2.]
9704b39
@jaspermdegroot jaspermdegroot referenced this issue from a commit
@jaspermdegroot jaspermdegroot Textinput: added conditional call to disable() to the create function…
… to make sure disabled elements get class ui-disabled. Fixes #4636 and #4637 - Text Input doesn't use ui-disabled class if disabled attribute is set in markup. [1.1.2.]
5edcb6e
@townxelliot townxelliot referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.