You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Vincent Spallek (Updated) (JIRA)" <ji...@apache.org> on 2012/04/05 15:17:24 UTC
[jira] [Updated] (FLEX-39)
mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores destroy
flag if CSS style modalTransparencyDuration is set to 0
[ https://issues.apache.org/jira/browse/FLEX-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Spallek updated FLEX-39:
--------------------------------
Description:
mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores the destroy flag if the CSS style modalTransparencyDuration is set to 0. In this case, the popup manager creates a memory leak. When destroy is set to true, it only sets the visibility of the modalWindow to false instead of removing it from its parent.
The algorithm for removing the modal window from its parent is implemented in mx.managers.PopUpManagerImpl.fadeOutDestroyEffectEndHandler(). This code probably has to be moved into a separate function and either be called directly from hideModalWindow() when destroy is true and modalTransparencyDuration is 0, otherwise from fadeOutDestroyEffectEndHandler().
was:
{{mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow()}} ignores the {{destroy}} flag if the CSS style {{modalTransparencyDuration}} is set to 0. In this case, the popup manager creates a memory leak. When {{destroy}} is set to {{true}}, it only sets the visibility of the modalWindow to {{false}} instead of removing it from its parent.
The algorithm for removing the modal window from its parent is implemented in {{mx.managers.PopUpManagerImpl.fadeOutDestroyEffectEndHandler()}}. This code probably has to be moved into a separate function and either be called directly from {{hideModalWindow()}} when {{destroy}} is {{true}} and {{modalTransparencyDuration}} is {{0}}, otherwise from {{fadeOutDestroyEffectEndHandler()}}.
> mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores destroy flag if CSS style modalTransparencyDuration is set to 0
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLEX-39
> URL: https://issues.apache.org/jira/browse/FLEX-39
> Project: Apache Flex
> Issue Type: Bug
> Environment: Flex 4.5.1; Flex 4.6.0
> Reporter: Vincent Spallek
> Assignee: Bertrand Delacretaz
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> mx.managers.PopUpManagerImpl.mx_internal::hideModalWindow() ignores the destroy flag if the CSS style modalTransparencyDuration is set to 0. In this case, the popup manager creates a memory leak. When destroy is set to true, it only sets the visibility of the modalWindow to false instead of removing it from its parent.
> The algorithm for removing the modal window from its parent is implemented in mx.managers.PopUpManagerImpl.fadeOutDestroyEffectEndHandler(). This code probably has to be moved into a separate function and either be called directly from hideModalWindow() when destroy is true and modalTransparencyDuration is 0, otherwise from fadeOutDestroyEffectEndHandler().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira