[
https://issues.apache.org/jira/browse/FLEX-29024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821169#comment-13821169
]
Jérôme Gillard commented on FLEX-29024:
---------------------------------------
I am afraid 'autoCorrect' and 'restrict' attributes are bound to TexInput
skinning.
When I use StageTextInputSkin, those properties are indeed working but I've got
several buggy behaviours.
To start with the most obvious, if you enter a something in your TextInput and
change the orientation of your device from portrait to landscape, the entered
word and focus caret are outside the actual TextInput. With both iOS and
Android System. More over, on Android Samsung devices that use kind of 'smart'
word suggestion keyboard, the system becomes totaly unusable (also the case for
Swype third-party keyboard).
This single problem makes TextInputSkin mandatory.
Should we open a bug about StageTextInputSkin or keep this bug open to try to
fix those properties for all skins?
> TextInput component ignores autoCapitalize, autoCorrect, and softKeyboardType
> properties when setting a custom skin
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FLEX-29024
> URL: https://issues.apache.org/jira/browse/FLEX-29024
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TextInput
> Affects Versions: Adobe Flex SDK 4.6 (Release)
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
> Reporter: Adobe JIRA
> Assignee: Maurice Amsellem
>
> Steps to reproduce:
> 1. add a textinput in a flex mobile project then do one or more of the
> following:
> 2. set the autoCapitalize property to "none"
> 3. set the autoCorrect property to "false"
> 4. set the softKeyboard property to "number"
> 5. create a custom skin and set the skin either in a css file or by setting
> the skin property of the component. (note: I have tried just making a skin
> as simple as extending the TextInputSkin with nothing else but calling the
> super() method, and I have tried coping the actual TextInputSkin myself and
> setting the skin to that file and the functionality will not work)
>
> Actual Results: Text input will still use autocorrect, auto capitalize and
> only show the regular keyboard. Removing the skin results in the
> functionality working properly.
>
>
> Expected Results: Text input with custom skin should not allow auto
> correcting or auto capitalization of text being typed, correct type of
> keyboard should appear as well.
>
>
> Workaround (if any): none
--
This message was sent by Atlassian JIRA
(v6.1#6144)
