flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mihai Chira (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-35321) LayoutManager initializes components which are no longer on stage
Date Mon, 14 Aug 2017 18:00:00 GMT

     [ 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).

----

*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}}.
*Unit test*: {{LayoutManager_FLEX_35321_Tests}}.

  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.

----

*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}}.
*Unit test*: {{LayoutManager_FLEX_35321_Tests}}.


> 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
>
>         Attachments: FLEX-35321 potential solution.patch
>
>
> *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).
> ----
> *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}}.
> *Unit test*: {{LayoutManager_FLEX_35321_Tests}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message