[
https://issues.apache.org/jira/browse/FLEX-33375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Harui resolved FLEX-33375.
-------------------------------
Resolution: Not A Problem
We would need a complete test case to be sure, but the most likely cause based
on the snippet you included is that the button still has keyboard focus. The
FocusManager does not try to figure out where else to put focus when the
focused item is removed from the display list. It is highly recommended that
you call setFocus on some useful component for your users that may not be able
to use a mouse, and doing so should allow the view to be garbage collected.
Otherwise, please re-open with a small and complete test case.
> Button clicked in a Component (Group) causes the component to stay in memory
> ----------------------------------------------------------------------------
>
> Key: FLEX-33375
> URL: https://issues.apache.org/jira/browse/FLEX-33375
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Button
> Environment: air 3.5 mobile
> Reporter: Christian Kiefer
> Priority: Critical
>
> Code:
> protected function handleLoginClicked(event:MouseEvent):void
> {
> dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123"));
> }
>
> ]]>
> </fx:Script>
> <s:Button width="100%" id="loginButton"
> enabled="true"
> label="test"
> height="60"
> click="handleLoginClicked(event)"/>
>
> <s:Label y="200" text="test" click="handleLoginClicked(event)"/>
> Result:
> After the login event is dispatched the view/current component (group) gets
> disposed and removed...
> Problem:
> clicking the label and the view isn't in memory anymore.
> clicking the button causes the view to stay in memory.
--
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
