[ 
https://issues.apache.org/jira/browse/FLEX-29024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820142#comment-13820142
 ] 

Jérôme Gillard commented on FLEX-29024:
---------------------------------------

This bug is blocking AIR bug reported at 
https://bugbase.adobe.com/index.cfm?event=bug&id=3605590 ( TextInput's restrict 
attribute makes user interaction totally unusable )
On a Samsung Galaxy SII, running Android 4.0.4 with it's Samsung default 
Keyboard, if the restrict attribute is set on a TextInput, the resulting text 
of user's input is not at all what he gets.
The text is partially overwritten with suggestions, or the prefix repeated on 
every char (making the text exponentially growing)

> 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
>
> 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)

Reply via email to