Filed issue FLEX-33773
2013/9/20 Alex Harui
> Yeah, please file a bug.
>
>
>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Cosma Colanicchia wrote:
>
>
> Checked with a 100ms timeout after the skinState change, focus is correctly
> on the RichEditableText instance. I think
Yeah, please file a bug.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Cosma Colanicchia wrote:
Checked with a 100ms timeout after the skinState change, focus is correctly
on the RichEditableText instance. I think the problem is that the
TLF container manager of RichEditableText
To try it out:
1) launch the app
2) keyboard tab to the text input
3) hit delete on keyboard
4) see that you can't type
5) tab again to move on button, hit spacebar to click
6) tab back to the text input
7) hit delete on keyboard
8) now it works correctly
And, alternative version
1) launch the a
Checked with a 100ms timeout after the skinState change, focus is correctly
on the RichEditableText instance. I think the problem is that the
TLF container manager of RichEditableText is not correctly updating.
Here is a simple snippet reproducing the problem with a plain TextInput
component.
htt
What is stage.focus? Maybe just assign it to the RichEditableText.
On 9/19/13 9:40 AM, "Cosma Colanicchia" wrote:
>Thank you Alex, but unfortunately the text input has to be focusable
>because it is part of a complex search component: it accept a query text
>and, on return, display a popup list
Thank you Alex, but unfortunately the text input has to be focusable
because it is part of a complex search component: it accept a query text
and, on return, display a popup list of results, once selected the text
input become not editable and display the selected item. In other words,
the user mov
Might be best to not allow focus if the control is not editable. Set
tabEnabled and/or focusEnabled=false.
On 9/19/13 2:45 AM, "Cosma Colanicchia" wrote:
>Hi, I have a little issue with the default TextInput component, could not
>find it in already logged issues - at least I think so, there are
Hi, I have a little issue with the default TextInput component, could not
find it in already logged issues - at least I think so, there are a lot of
issues about text input components.
This is the scenario:
1) the component instance start with editable="false"
2) user moves focus to component usi
