[TIMOB-2113] iOS keyboard, unable to turn off Autocorrect
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Hold |
Resolution Date | 2011-04-15T03:10:48.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Backlog |
Components | iOS |
Labels | apple, bug, ios, keyboard, regression |
Reporter | Thomas Huelbert |
Assignee | Blain Hamon |
Created | 2011-04-15T03:10:47.000+0000 |
Updated | 2017-03-03T07:01:39.000+0000 |
Description
iPod 4th gen (4.1), 3rd gen 4.0.2 with mobile sdk build 1.5.0.62c1cae
1.BaseUI>TextField>The rest
2.toggle auto correct, then type some text that would invoke
autocorrect.
3.toogle again and try
results: unable to turn it off, auto correct kicks in for second word - first word is not auto corrected.
Bug results from the fact that keyboard autocorrect default is YES, and we initially report autocorrect as NO (doing it the other way around is problematic). Looking for a way to determine the initial autocorrect value, or into a possible third value ('auto').
(from [698708bb1c306e4f221bb2f6380b1fa7b0642d52]) [#2113] Textfield test now unambiguously sets autocorrect/autocap values before testing. http://github.com/appcelerator/titanium_mobile/commit/698708bb1c306e4f221bb2f6380b1fa7b0642d52"> http://github.com/appcelerator/titanium_mobile/commit/698708bb1c306...
Changing to needs-more-info so we can talk this one over with the Android guys, so that we can all support a third 'auto' value (if possible).
Going to mark this as an Apple bug. I was able to recreate it in the following scenario:
Looks like autocorrect settings don't take place until after editing is finished. Radar bug # is 8703310.
Should we force a blur and focus to fix it?
Closing ticket due to time passed and irrelevance.