Skip to content
This repository

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

Closed
patrick-wolf opened this Issue July 03, 2012 · 2 comments

2 participants

Patrick Wolf Jasper de Groot
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.

Jasper de Groot
Owner

@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!

Jasper de Groot uGoMobi closed this issue from a commit July 03, 2012
Jasper de Groot 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
Jasper de Groot uGoMobi closed this in 9704b39 July 03, 2012
Jasper de Groot uGoMobi referenced this issue from a commit July 03, 2012
Jasper de Groot 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
Elliot Smith townxelliot referenced this issue from a commit July 30, 2012
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.