[
https://issues.apache.org/jira/browse/FLEX-34187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Chira updated FLEX-34187:
-------------------------------
Description:
Steps to reproduce:
1. Run the attached project
2. Hover mouse over the first button (and don't move it)
2.1. Notice that the mouseOut event was called.
3. Hover mouse over the second button (and don't move it)
Actual behaviour: mouseOut is not dispatched when the button is removed from
stage, but only when the user moves the mouse again.
Expected behaviour: mouseOut is dispatched as soon as the button is removed
from stage, regardless which component had focus when the hovered button was
removed.
NOTES:
-this bug is reproducible regardless which component we set the focus to before
removing the second button.
-this bug is reproducible with any type of component, not just Buttons, as long
as you can add a MOUSE_OUT event listener to it.
-this is most likely the cause of FLEX-34188.
was:
Steps to reproduce:
1. Run the attached project
2. Hover mouse over the first button (and don't move it)
2.1. Notice that the mouseOut event was called.
3. Hover mouse over the second button (and don't move it)
Actual behaviour: mouseOut is not dispatched when the button is removed from
stage, but only when the user moves the mouse again.
Expected behaviour: mouseOut is dispatched as soon as the button is removed
from stage, regardless which component had focus when the hovered button was
removed.
NOTES:
-this bug is reproducible regardless which component we set the focus to before
removing the second button.
-this bug is reproducible with any type of component, not just Buttons, as long
as you can add a MOUSE_OUT event listener to it.
> mouseOut event not dispatched on component removal if setFocus() called
> -----------------------------------------------------------------------
>
> Key: FLEX-34187
> URL: https://issues.apache.org/jira/browse/FLEX-34187
> Project: Apache Flex
> Issue Type: Bug
> Components: Focus Manager
> Affects Versions: Apache Flex 4.11.0
> Reporter: Mihai Chira
> Labels: easytest
> Fix For: Apache Flex 4.13.0
>
> Attachments: _MouseOutGlitch.fxp
>
>
> Steps to reproduce:
> 1. Run the attached project
> 2. Hover mouse over the first button (and don't move it)
> 2.1. Notice that the mouseOut event was called.
> 3. Hover mouse over the second button (and don't move it)
> Actual behaviour: mouseOut is not dispatched when the button is removed from
> stage, but only when the user moves the mouse again.
> Expected behaviour: mouseOut is dispatched as soon as the button is removed
> from stage, regardless which component had focus when the hovered button was
> removed.
> NOTES:
> -this bug is reproducible regardless which component we set the focus to
> before removing the second button.
> -this bug is reproducible with any type of component, not just Buttons, as
> long as you can add a MOUSE_OUT event listener to it.
> -this is most likely the cause of FLEX-34188.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
