flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Childs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-34029) Modal popup closed too quickly disables all input on window
Date Wed, 08 Jan 2014 15:15:53 GMT

     [ https://issues.apache.org/jira/browse/FLEX-34029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colin Childs updated FLEX-34029:
--------------------------------

    Attachment: Test.fxp

I have attached a project that replicates the issue

> Modal popup closed too quickly disables all input on window
> -----------------------------------------------------------
>
>                 Key: FLEX-34029
>                 URL: https://issues.apache.org/jira/browse/FLEX-34029
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Mobile: SkinnablePopUpContainer
>    Affects Versions: Apache Flex 4.11.0
>            Reporter: Colin Childs
>         Attachments: Test.fxp
>
>
> When creating a popup for a mobile app using a SkinnablePopUpContainer, closing it quickly
after opening will remove the popup from the screen, but the modal aspect remains, preventing
any touch interactions. This gives the appearance of the app being unresponsive and looks
as though it has crashed. I noticed this with a loading dialog which would close really quickly
when performing operations on faster devices or with users with little data. It is easy to
reproduce by creating a simple mobile project and closing a modal popup immediately after
opening it. I suspect that the FlexEvent.STATE_CHANGE_COMPLETE even does not fire when the
popup is closed too quickly, which prevents SkinnablePopUpContainer's stateChangeComplete_handler
function from being called.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message