[
https://issues.apache.org/jira/browse/FLEX-28807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720454#comment-13720454
]
Saurabh Jain commented on FLEX-28807:
-------------------------------------
Another issue that comes up here is in the following scenarion:
1. Assume that you have a keyboard event listener added in your popup/title
window; say for ESC key close popup.
2. Open the popup and press ESC key. This will work fine
2. Now again open the popup and open up a new tab. Come back to the original
tab and try pressing the ESC key now. This does not work now. The keyboard
events are no more listened because the focus in not set :( ???. The only
solution that I could think of here there should be some mouse down event which
should set focus for some child. I know this is pretty bad solution but this is
what I could think.
Do you have any better solution???
Thanks for your time.
Cheers
Saurabh
> s:TitleWindow didn't get focus when user click on moveArea until one of its
> children get the focus
> --------------------------------------------------------------------------------------------------
>
> Key: FLEX-28807
> URL: https://issues.apache.org/jira/browse/FLEX-28807
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TitleWindow
> Affects Versions: Adobe Flex SDK 4.5.1 (Release)
> Environment: Affected OS(s): Windows
> Affected OS(s): Windows XP
> Browser: Firefox 3.x
> Language Found: English
> Reporter: Adobe JIRA
> Attachments: DummyApp.mxml
>
>
> Steps to reproduce:
> 1. Create a TitleWindow in a PopUp.
> 2. Attach a listener for the FOCUS_IN event on the titleWindow instance.
> 3. Click on the move area (an eventually move the TitleWindow around)
>
> Actual Results:
> The listener is not called.
>
> Expected Results:
> The listener should be called.
>
> Workaround (if any):
> Set the focus on one of the TitleWindow children, after that when the
> TitleWindow lose the focus, clicking on the moveArea is enough to get the
> focus on the TitleWindow.
>
> You can find in attachment a dummy App to demonstrate the bug, uncomment the
> line 66 workaround the issue (but adding an invisible button only for that
> purpose looks a bad idea :-)
--
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
