[FLEX-28430] Group.removeAllElements() with removedEffect causes RTE

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Adobe Flex SDK 4.5.1 (Release)
• Component/s: Spark: Group
• Environment: Affected OS(s): All OS Platforms; Affected OS(s): All OS Platforms; Browser: Internet Explorer 8.x; Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 05/Sep/11 05:58
• Updated: 11/Oct/11 07:23
• Resolved: 29/Jan/12 03:22

Description

Steps to reproduce:
1. Run code:

<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
<fx:Style>
@namespace s "library://ns.adobe.com/flex/spark";
@namespace mx "library://ns.adobe.com/flex/mx";
s|Button

{ addedEffect: Fade; removedEffect: Fade; }

</fx:Style>
<s:layout>
<s:VerticalLayout />
</s:layout>
<s:Button label="Remove All" click="group.removeAllElements()" />
<s:Group id="group">
<s:layout>
<s:VerticalLayout />
</s:layout>
<s:Button label="b1"/>
<s:Button label="b2"/>
<s:Button label="b3"/>
</s:Group>
</s:Application>

2. Press Remove All button

Actual Results:
RangeError: Index 2 is out of range.
at spark.components::Group/checkForRangeError()[E:\dev\4.0.0\frameworks\projects\spark\src\spark\components\Group.as:1106]
at spark.components::Group/addElementAt()[E:\dev\4.0.0\frameworks\projects\spark\src\spark\components\Group.as:1158]
at mx.effects::EffectManager$/removedEffectHandler()[E:\dev\4.0.0\frameworks\projects\framework\src\mx\effects\EffectManager.as:799]
at Function/http://adobe.com/AS3/2006/builtin::apply()
at mx.core::UIComponent/callLaterDispatcher2()[E:\dev\4.0.0\frameworks\projects\framework\src\mx\core\UIComponent.as:11354]
at mx.core::UIComponent/callLaterDispatcher()[E:\dev\4.0.0\frameworks\projects\framework\src\mx\core\UIComponent.as:11292]

Expected Results:
No RTE, child components to be removed with their associated remove effect.

Workaround (if any):
None currently.
NB: Fix required for SDK 4.1 onwards.