[TIMOB-1795] autocorrect, autocapitalization properties undocumented for TextField, TextArea
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Trivial |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-04-17T01:57:11.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | iOS |
Labels | apidoc, autocapitalization, autocorrect, textarea, textfield |
Reporter | Brion Vibber |
Assignee | Blain Hamon |
Created | 2011-04-15T03:02:37.000+0000 |
Updated | 2011-04-17T01:57:11.000+0000 |
Description
API documentation for TextField and TextArea do not document the
autocorrect or autocapitalization properties:
https://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI.TextField-object">
https://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI...
https://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI.TextArea-object">
https://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI...
Note that there is some documentation for those properties on
SearchBar:
https://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI.SearchBar-object">
https://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI...
however it lists autocapitalization as a boolean, while the TextField and TextArea appear to accept enumerated values such as Titanium.UI.TEXT_AUTOCAPITALIZATION_NONE, Titanium.UI.TEXT_AUTOCAPITALIZATION_WORDS, and Titanium.UI.TEXT_AUTOCAPITALIZATION_SENTENCES.
Assigning to our support contact for StatusNet.
There is another LH ticket, perhaps in the Android space, which has notes from discussing this issue with the Android folks. I don't know if that ticket was closed, but the notes above indicate the four states Android employs (NONE, SENTENCES, WORDS, and ALL), but not include the proposed "Auto" state (Perhaps that was closed or resolved as "what does 'auto' mean?).
Checked docs 1.6.0GM.