Disabled the workaround for issue 785 (jQM text input forces use of iOS auto-correction) on iOS 5 devices since it appears to be fixed. This is still a problem on iOS 4.x and earlier.

- We don't have a specific test for iOS 5 so we use $.support.touchOverflow as an iOS 5 and later indicator. Yes, I feel dirty.
This commit is contained in:
Kin Blas 2011-09-26 11:39:30 -07:00
parent 6cd1e1b141
commit a975878fb4

View file

@ -34,11 +34,14 @@ $.widget( "mobile.textinput", $.mobile.widget, {
focusedEl = input;
// XXX: Temporary workaround for issue 785. Turn off autocorrect and
// autocomplete since the popup they use can't be dismissed by
// the user. Note that we test for the presence of the feature
// by looking for the autocorrect property on the input element.
if ( typeof input[0].autocorrect !== "undefined" ) {
// XXX: Temporary workaround for issue 785 (Apple bug 8910589).
// Turn off autocorrect and autocomplete on non-iOS 5 devices
// since the popup they use can't be dismissed by the user. Note
// that we test for the presence of the feature by looking for
// the autocorrect property on the input element. We currently
// have no test for iOS 5 or newer so we're temporarily using
// the touchOverflow support flag for jQM 1.0. Yes, I feel dirty. - jblas
if ( typeof input[0].autocorrect !== "undefined" && !$.support.touchOverflow ) {
// Set the attribute instead of the property just in case there
// is code that attempts to make modifications via HTML.
input[0].setAttribute( "autocorrect", "off" );