You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Mihai Chira (JIRA)" <ji...@apache.org> on 2017/06/05 11:45:04 UTC
[jira] [Updated] (FLEX-35321) LayoutManager initializes components
which are no longer on stage
[ https://issues.apache.org/jira/browse/FLEX-35321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mihai Chira updated FLEX-35321:
-------------------------------
Description:
*Scenario A*: during an object's validation cycle some code resulting from {{validateSize()}}, {{validateProperties()}} or {{validateDisplayList()}} results in the object's removal from stage.
*Scenario B*: a user performs an action whose effect is the removal of a component, exactly when that component is being validated in phases ({{LayoutManager.usePhasedInstantiation == true}}, which is to say, in the span of two-three frames.
(For the unit test that models this scenario, see {{LayoutManagerTests}}.)
----
*Expected behaviour*: {{LayoutManager}} detects the object's removal from stage, stops validating it, and never sets its {{initialized}} flag to {{true}}.
*Actual behaviour*: {{LayoutManager}} does not detect the object's removal from stage, continues validating it, and ends up setting the object's {{initialized}} flag to {{true}}.
was:
*Scenario A*: during an object's validation cycle some code resulting from {{validateSize()}}, {{validateProperties()}} or {{validateDisplayList()}} results in the object's removal from stage.
*Scenario B*: a user performs an action whose effect is the removal of a component, exactly when that component is being validated in phases ({{LayoutManager.usePhasedInstantiation == true}}, which is to say, in the span of two-three frames.
(For the unit test that models this scenario, see {{LayoutManagerTests}}.)
*Expected behaviour*: {{LayoutManager}} detects the object's removal from stage, stops validating it, and never sets its {{initialized}} flag to {{true}}.
*Actual behaviour*: {{LayoutManager}} does not detect the object's removal from stage, continues validating it, and ends up setting the object's {{initialized}} flag to {{true}}.
> LayoutManager initializes components which are no longer on stage
> -----------------------------------------------------------------
>
> Key: FLEX-35321
> URL: https://issues.apache.org/jira/browse/FLEX-35321
> Project: Apache Flex
> Issue Type: Bug
> Components: Layout - General
> Affects Versions: Apache Flex 4.16.0
> Reporter: Mihai Chira
> Assignee: Mihai Chira
> Fix For: Apache Flex 4.17.0
>
>
> *Scenario A*: during an object's validation cycle some code resulting from {{validateSize()}}, {{validateProperties()}} or {{validateDisplayList()}} results in the object's removal from stage.
> *Scenario B*: a user performs an action whose effect is the removal of a component, exactly when that component is being validated in phases ({{LayoutManager.usePhasedInstantiation == true}}, which is to say, in the span of two-three frames.
> (For the unit test that models this scenario, see {{LayoutManagerTests}}.)
> ----
> *Expected behaviour*: {{LayoutManager}} detects the object's removal from stage, stops validating it, and never sets its {{initialized}} flag to {{true}}.
> *Actual behaviour*: {{LayoutManager}} does not detect the object's removal from stage, continues validating it, and ends up setting the object's {{initialized}} flag to {{true}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)