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

Maurice Amsellem commented on FLEX-34145:
-----------------------------------------

FIXED - FLEX-34145 Mobile Theme: TextInput with layoutDirection="rtl" becomes 
mirror on focus out.
I also fixed the text field placement error when layoutDirection is set at the 
app level.
(so case 1, 2 and 3 are fixed) 

Project: http://git-wip-us.apache.org/repos/asf/flex-sdk/repo
Commit: http://git-wip-us.apache.org/repos/asf/flex-sdk/commit/787addb6
Tree: http://git-wip-us.apache.org/repos/asf/flex-sdk/tree/787addb6
Diff: http://git-wip-us.apache.org/repos/asf/flex-sdk/diff/787addb6


> Mobile Theme: TextInput with layoutDirection="rtl" becomes mirror on focus 
> out.
> -------------------------------------------------------------------------------
>
>                 Key: FLEX-34145
>                 URL: https://issues.apache.org/jira/browse/FLEX-34145
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: TextInput
>    Affects Versions: Apache Flex 4.12.0
>         Environment: mobile project
>            Reporter: Ori Segal
>            Assignee: Maurice Amsellem
>
> After upgrading to version 4.12 TextInput component defined to be with RTL 
> layoutDirection is mirroring the text after focus-out.
> When typing the text looks OK, but when leaving the field the text becomes
> LTR and in fact becomes mirror writing.
> Note that it worked great on version 4.11.
> Here is a video the that shows issue.
> http://screencast.com/t/ekJnaDOZ6H
> The following example can be used to demonstrate the issue -
> <?xml version="1.0" encoding="utf-8"?>
> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009";
>                         xmlns:s="library://ns.adobe.com/flex/spark"
> applicationDPI="160">
>        <s:TextInput layoutDirection="rtl" direction="rtl" />
> </s:Application>



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

Reply via email to