Mailing-List: contact issues-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Date: Mon, 26 May 2014 14:33:01 +0000 (UTC)
From: =?utf-8?Q?J=C3=A9r=C3=B4me_Gillard_=28JIRA=29?= <jira@apache.org>
To: issues@flex.apache.org
Message-ID: <JIRA.12679217.1384437143366.18180.1401114781745@arcas>
In-Reply-To: <JIRA.12679217.1384437143366@arcas>
References: <JIRA.12679217.1384437143366@arcas>
Subject: [jira] [Updated] (FLEX-33905) TextInput component with restrict
 property is not working with Samsung default keyboard
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/FLEX-33905?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=A9r=C3=B4me Gillard updated FLEX-33905:
----------------------------------

    Description:=20
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 TextInpu=
t, 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 a=
t the first focus in event.

EDIT: also tested with the new spark.skins.mobile.ScrollingStageTextInputSk=
in. Same unexpected behaviour.

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 N=
OK
- Default TextInput with TextInputSkin: "abc abc" -> OK
- Restricted TextInput with TextInputSkin: "ababc" -> NOK, one "C" is missi=
ng!


Expected Result:

- In all TextInputs: "abc abc"

Any Workarounds:

Write word char by char.=20

  was:
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 TextInpu=
t, 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 a=
t 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 N=
OK
- Default TextInput with TextInputSkin: "abc abc" -> OK
- Restricted TextInput with TextInputSkin: "ababc" -> NOK, one "C" is missi=
ng!


Expected Result:

- In all TextInputs: "abc abc"

Any Workarounds:

Write word char by char.=20


> TextInput component with restrict property is not working with Samsung de=
fault 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), Apache Flex 4.12.1
>         Environment: Samsung Galaxy SII, running Android 4.0.4 with it's =
Samsung default Keyboard.=20
> Flex 4.6.0 AIR 3.8
> Flex 4.12.1 AIR 13.0
>            Reporter: J=C3=A9r=C3=B4me Gillard
>              Labels: easytest, mobileTextInput
>         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 TextIn=
put, the resulting text of user's input is not at all what he gets.
> The text is partially overwritten with suggestions, or the prefix repeate=
d 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.
> EDIT: also tested with the new spark.skins.mobile.ScrollingStageTextInput=
Skin. Same unexpected behaviour.
> 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 mis=
sing!
> Expected Result:
> - In all TextInputs: "abc abc"
> Any Workarounds:
> Write word char by char.=20


--
This message was sent by Atlassian JIRA
(v6.2#6252)