{ "id": "62745", "key": "TIMOB-2113", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11258", "description": "Holding Pen for Triaged Issues", "name": "Backlog", "archived": false, "released": false } ], "resolution": { "id": "6", "description": "", "name": "Hold" }, "resolutiondate": "2011-04-15T03:10:48.000+0000", "created": "2011-04-15T03:10:47.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "apple", "bug", "ios", "keyboard", "regression" ], "versions": [], "issuelinks": [], "assignee": { "name": "blainhamon", "key": "blainhamon", "displayName": "Blain Hamon", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-03T07:01:39.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
iPod 4th gen (4.1), 3rd gen 4.0.2 with mobile sdk build\n1.5.0.62c1cae
\n1.BaseUI>TextField>The rest
\n2.toggle auto correct, then type some text that would invoke\nautocorrect.
\n3.toogle again and try
results: unable to turn it off, auto correct kicks in for second\nword - first word is not auto corrected.
Bug results from the fact that keyboard autocorrect default is\nYES, and we initially report autocorrect as NO (doing it the other\nway around is problematic). Looking for a way to determine the\ninitial autocorrect value, or into a possible third value\n('auto').
(from [698708bb1c306e4f221bb2f6380b1fa7b0642d52])\n[#2113] Textfield test now unambiguously sets\nautocorrect/autocap values before testing. \nhttp://github.com/appcelerator/titanium_mobile/commit/698708bb1c306...
Changing to needs-more-info so we can talk this one over with\nthe Android guys, so that we can all support a third 'auto' value\n(if possible).
Going to mark this as an Apple bug. I was able to recreate it in\nthe following scenario:
\nLooks like autocorrect settings don't take place until after\nediting is finished. Radar bug # is 8703310.
Should we force a blur and focus to fix it?