flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cosma Colanicchia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33773) TextInput can't be made programmat‚Äčically editable while it already has focus
Date Mon, 23 Sep 2013 12:13:12 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cosma Colanicchia updated FLEX-33773:
-------------------------------------

    Attachment: TextInputTest.mxml

Attached sample app TextInputTest.mxml

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
6) tab back to the text input
7) hit delete on keyboard
8) now it works correctly

Also:
1) launch the app
2) click with mouse on the text input to focus it
3) hit delete on keyboard
4) you can type correctly

You can verify using the bottom label that the stage focus is always on the RichEditableText.
                
> TextInput can't be made programmat‚Äčically editable while it already has focus
> -----------------------------------------------------------------------------
>
>                 Key: FLEX-33773
>                 URL: https://issues.apache.org/jira/browse/FLEX-33773
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: TextInput
>    Affects Versions: Apache Flex 4.11.0
>         Environment: Windows 7 64bit
>            Reporter: Cosma Colanicchia
>            Priority: Minor
>         Attachments: TextInputTest.mxml
>
>
> This is the scenario:
> 1) the component instance start with editable="false"
> 2) user moves focus to component using the keyboard
> 3) a particular key press activates editability of the field (through a custom keyDown
listener)
> 4) no cursor displayed, can't type in the field
> Notes:
>  - this is happening with the default (TLF-based) TextInput skin
>  - moving away focus and getting back to it (with keyboard or mouse, or even with an
ALT-TAB) cause the component to start behaving correctly
>  - if the instance has been previously editable, the behavior doesn't reproduce
>  - if the focus is moved to the component through a mouse click the issue is not triggered
> As a workaround, I tried a callLater(textInput.setFocus) on my custom keyDown listener,
without success. Replacing the callLater with a setTimeout also doesn't work (in both cases,
it seems that its setFocus() override of RichEditableText does nothing because the check on
the compose state of the text container manager.

--
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

Mime
View raw message