Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: TLF IME
From: Harbs <harbs.lists@gmail.com>
In-Reply-To: <D20C673B.39577%aharui@adobe.com>
Date: Thu, 3 Sep 2015 15:19:53 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0CA81D7C-100B-435B-8682-96F80DDD5673@gmail.com>
References: <C2629F59-D023-44AE-BBDA-255F35078D91@gmail.com>
 <D447F923-45E5-4867-BBE7-AE66E21FB050@gmail.com>
 <D20B0C9C.39420%aharui@adobe.com>
 <700EF7C0-5A48-4AE6-87C6-6EA20047F5D2@gmail.com>
 <D20BD115.394F3%aharui@adobe.com>
 <CE0CCA71-7DA4-41B1-9EC7-60AC9FA87F67@gmail.com>
 <D20C673B.39577%aharui@adobe.com>
To: dev@flex.apache.org

FWIW, I did not figure out what was disabling the IME.

I did figure out how to get the IME working though. When the TextFlow =
gets focus, I just added IME.enabled =3D true;

For the sake of completeness I=92m documenting my observations of IME =
behavior:

IME works inline on all Windows browsers and in Chrome on Mac. On Mac =
Firefox and Safari, it shows up in a dialog on the bottom of the screen. =
I have not checked other browsers. It=92s worthy of note that I had my =
issues on browsers where IME is inline. I still have a suspicion that =
something changed in the Flash plugin, but since things are working =
again, I=92m happy leaving good enough alone.

On Sep 2, 2015, at 6:44 PM, Alex Harui <aharui@adobe.com> wrote:

> Can you switch back to Adobe Flex 4.6?  Or whatever version of Apache =
Flex
> was before we started deferring focus changes to TextInputs?
>=20
> -Alex
>=20
> On 9/2/15, 2:29 AM, "Harbs" <harbs.lists@gmail.com> wrote:
>=20
>> Neither of those two seem to be in use. I=92m exploring other focus
>> redirecting possibilities, but so far no luck=85
>>=20
>> On Sep 2, 2015, at 8:03 AM, Alex Harui <aharui@adobe.com> wrote:
>>=20
>>> IIRC, there can be issues if parent display objects have tabEnabled
>>> and/or
>>> tabChildren set to false.
>>>=20
>>> -Alex
>>>=20
>>> On 9/1/15, 9:32 AM, "Harbs" <harbs.lists@gmail.com> wrote:
>>>=20
>>>> OK.
>>>>=20
>>>> I just put together a non-Flex case and it seems to work in all =
three
>>>> Mac
>>>> browsers:
>>>>=20
>>>> package
>>>> {
>>>> 	import flash.display.Sprite;
>>>> 	import flash.system.Capabilities;
>>>> 	import flash.system.IME;
>>>> 	import flash.text.TextField;
>>>> 	import flash.text.TextFieldType;
>>>> =09
>>>> 	public class IMETest extends Sprite
>>>> 	{
>>>> 		public function IMETest()
>>>> 		{
>>>> 			if (Capabilities.hasIME)
>>>> 			{=20
>>>> 				IME.enabled =3D true;
>>>> 			}=20
>>>> 			tField.type =3D TextFieldType.INPUT;
>>>> 			tField.width =3D 100;
>>>> 			tField.height =3D 18;
>>>> 			tField.background =3D true;
>>>> 			tField.border =3D true;
>>>> 			addChild(tField);
>>>>=20
>>>> 		}
>>>> 		private var tField:TextField =3D new TextField();
>>>> 	=09
>>>> 	}
>>>> }
>>>>=20
>>>> So, I guess there is a Flex problem here=85
>>>> Things are clearly more complicated than I thought, because this =
works
>>>> in
>>>> all browsers (on Mac).
>>>>=20
>>>> <?xml version=3D"1.0" encoding=3D"utf-8"?>
>>>> <s:Application xmlns:fx=3D"http://ns.adobe.com/mxml/2009"
>>>> 			   xmlns:s=3D"library://ns.adobe.com/flex/spark"
>>>> 			   xmlns:mx=3D"library://ns.adobe.com/flex/mx" =
minWidth=3D"955"
>>>> minHeight=3D"600" backgroundColor=3D"#FFFF00" =
backgroundAlpha=3D"0.5">
>>>> 	<fx:Declarations>
>>>> 		<!-- Place non-visual elements (e.g., services, value =
objects) here
>>>> -->
>>>> 	</fx:Declarations>
>>>> 	<s:RichEditableText text=3D"Some text here..." editable=3D"true"
>>>> width=3D"200"
>>>> height=3D"50" backgroundColor=3D"#FFFFFF"/>
>>>> </s:Application>
>>>>=20
>>>> Thanks for pointing me in the right direction. I=92ll have to =
figure out
>>>> why it=92s not working in my app=85
>>>>=20
>>>> On Sep 1, 2015, at 6:05 PM, Alex Harui <aharui@adobe.com> wrote:
>>>>=20
>>>>> First, build a non-Flex test case.  Then file that test case at
>>>>> bugbase.adobe.com.
>>>>>=20
>>>>> -Alex
>>>>>=20
>>>>> On 9/1/15, 7:48 AM, "Harbs" <harbs.lists@gmail.com> wrote:
>>>>>=20
>>>>>> I=92m not sure if this is a TLF issue or a Flash player issue.
>>>>>>=20
>>>>>> I=92m getting different results in different browsers. Who would =
we
>>>>>> contact
>>>>>> at Adobe to report this issue in Flash?
>>>>>>=20
>>>>>> On Aug 31, 2015, at 11:59 AM, Harbs <harbs.lists@gmail.com> =
wrote:
>>>>>>=20
>>>>>>> It looks to me that IME is completely broken in the recent =
versions
>>>>>>> of
>>>>>>> TLF. It seems to work in Firefox and Safari on Mac (at least at =
the
>>>>>>> bottom of the screen), but does not work in Chrome on Mac or any
>>>>>>> browser
>>>>>>> on Windows.
>>>>>>>=20
>>>>>>> Has anyone else noticed this?
>>>>>>>=20
>>>>>>> Harbs
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20