flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34339) Components don't focusOut when removed from stage
Date Thu, 26 Jun 2014 16:33:24 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044826#comment-14044826

Alex Harui commented on FLEX-34339:

I think testing index change is probably sufficient.  Really, the focused object shouldn't
be going through a bunch of display list changes.  Another change is re-parenting.  That can
happen when you pop a UI widget to the front and I think that also does a remove/add.

For sure, you are not the first person to complain about this SDK behavior.  I've just been
too chicken to try to take the time to work on it when I think eventually, you'll change your
app to set focus some place anyway.  But if this is something you want to work on, go for
it.  That's the Apache Way.

> Components don't focusOut when removed from stage
> -------------------------------------------------
>                 Key: FLEX-34339
>                 URL: https://issues.apache.org/jira/browse/FLEX-34339
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: .Unspecified - Framework
>    Affects Versions: Apache Flex 4.12.0
>            Reporter: Mihai Chira
>              Labels: easytest
>             Fix For: Apache Flex 4.13.0
>         Attachments: _focusOutNotDispatchedOnRemove.fxp
> *Steps to reproduce*:
> 1. Import and run attached project.
> 2. Click on numeric stepper and then on button. Notice that focusIn and focusOut events
are dispatched by numeric stepper as expected.
> 3. Shift+Click on the numeric stepper (this will remove it from stage in 600ms).
> *Actual behaviour*: focusOut is not dispatched by numeric stepper when it's removed from
> *Desired behaviour*: I expect that a focused component should be de-focused when removed
from stage.
> *NOTES*:
> -This causes at least one other bug: FLEX-34340.
> -Not sure if this is a flash player bug or SDK bug. Or it could be a feature, but definitely
not an intuitive one.
> -I have a feeling this is related to FLEX-20416 (couldn't check, since the attachment
is not on the ticket).

This message was sent by Atlassian JIRA

View raw message