Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Date: Wed, 29 Aug 2012 23:20:08 +1100 (NCT)
From: "Al Birdy (JIRA)" <jira@apache.org>
To: flex-dev@incubator.apache.org
Message-ID: <1985842282.11426.1346242808121.JavaMail.jiratomcat@arcas>
In-Reply-To: <791930653.84021.1342819056827.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (FLEX-33143) Spark TextInput using Mobile
 skinClass: setting displayAsPassword to true impacts all other TextInput
 and breaks softKeyBoard (no more International keyboards)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Al Birdy commented on FLEX-33143:
---------------------------------

So you basically just removed the skinclass allocation from your TextInput's as the default skin already is the StageTextInputSkin, correct?
Or did you specifically set the StageTextInputSkin?
                
> Spark TextInput using Mobile skinClass: setting displayAsPassword to true impacts all other TextInput and breaks softKeyBoard (no more International keyboards)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-33143
>                 URL: https://issues.apache.org/jira/browse/FLEX-33143
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: TextInput
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: IPAD AIR 3.3
>            Reporter: Philippe Mouawad
>            Priority: Critical
>         Attachments: BUG-33143.fxp
>
>
> Hello,
> We have a mobile application that uses Flex 4.6 (Air 3.3) that is deployed on Android Tablets and IPad ones (IPad 1 & 2, IOS 5.1.1 9B296).
> Users from Thailang / Korea are reporting a problem with the soft keyboard which does not propose the Thai or Korean keyboard while native application do propose it.
> To be clear, on iPad you can configure more than one keyboard among which for example Thai or Korean keyboards.
>     http://support.apple.com/kb/HT4509
> I searched for some time, and finally came to a strange idea. I noticed my first TextInput fields had displayAsPassword set to true.
> So I made a little test with:
>     1)<s:TextInput/>
> and
>     2) <s:TextInput displayAsPassword="true" />
> And BINGO, there is a bug:
> 1) If I first go to first field, International Keyboard appears
> 2) I go to second one, it disappears
> 3) I go back to first one, no more International Keyboard
> Setting displayAsPassword="true" breaks soft keyboard.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira