flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jérôme Gillard (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (FLEX-33905) TextInput component with restrict property is not working with Samsung default keyboard
Date Thu, 14 Nov 2013 13:55:21 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jérôme Gillard updated FLEX-33905:
----------------------------------

    Comment: was deleted

(was: Test project.)

> TextInput component with restrict property is not working with Samsung default keyboard
> ---------------------------------------------------------------------------------------
>
>                 Key: FLEX-33905
>                 URL: https://issues.apache.org/jira/browse/FLEX-33905
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Mobile: SoftKeyboard, Mobile: Text, Spark: TextInput
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: Samsung Galaxy SII, running Android 4.0.4 with it's Samsung default
Keyboard. 
> Flex 4.6.0 AIR 3.8
>            Reporter: Jérôme Gillard
>              Labels: textinput, textinputskin
>         Attachments: samsungpredictivetext_bug.fxp
>
>
> Problem Description: 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)
> Applying spark.skins.mobile.TextInputSkin doesn't solve the problem.
> Moreover, when TextInputSkin if applied, the softkeyboard doesn't show up at the first
focus in event.
> See attached project to reproduce.
> Steps to Reproduce:
> 1 - Install attached project
> 2 - In each visible TextInput
> 3 - hit those letters on the softKeyboard: "a", "b", "c".
> 4 - Select "abc" suggested by Samsung's keyboard
> 5 - Repeat step 3.
> 6 - Repeat step 4, your goal is to write "abc".
> 7 - See what you have inside TextInputs
> Actual Result:
> - Default TextInput, with default Skin: "abc abc" -> OK
> - Restricted TextInput with default Skin: "abcabcabcabcabcabc" -> totally NOK
> - Default TextInput with TextInputSkin: "abc abc" -> OK
> - Restricted TextInput with TextInputSkin: "ababc" -> NOK, one "C" is missing!
> Expected Result:
> - In all TextInputs: "abc abc"
> Any Workarounds:
> Write word char by char. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message