Skip to content

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

Closed
patrick-wolf opened this Issue Jul 3, 2012 · 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
jQuery Foundation member

@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 added a commit that closed this issue Jul 3, 2012
@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 added a commit that referenced this issue Jul 12, 2012
@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
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.