[
https://issues.apache.org/jira/browse/FLEX-28807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719779#comment-13719779
]
Alex Harui commented on FLEX-28807:
-----------------------------------
This is "not a bug" in the sense that the FocusManager is currently designed to
work this way. It does not try to auto-assign focus to some widget in a popup.
It assumes you will do so (which is a good practice for accessibility
reasons). The reason FocusManager doesn't auto-assign is that it doesn't want
to waste time trying to figure out the best place to assign focus, and/or
create timing issues where your code does that just before the FocusManager
auto-assign runs. But enough folks have hit variations of this issue that it
might be worth trying out auto-assign code and see if we get more or fewer
complaints.
> 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
