[FLEX-27926] Setting mxmlContent on a SkinnableContainer doesn't dispatch ElementExistenceEvents

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Adobe Flex SDK 4.6 (Release)
• Fix Version/s: Adobe Flex SDK Next
• Component/s: Spark: SkinnableContainer
• Environment: Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 26/Jul/11 15:36
• Updated: 15/Nov/11 16:14
• Resolved: 30/Sep/11 09:57

Description

Steps to reproduce:
1. Run the following 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">
<s:layout>
<s:VerticalLayout />
</s:layout>

<fx:Script>
<![CDATA[
import spark.events.ElementExistenceEvent;

protected function elementAddHandler1(event:ElementExistenceEvent):void

{ label1.text = "mxmlContent: add event received"; }

protected function elementAddHandler2(event:ElementExistenceEvent):void

{ label2.text = "mxmlContentFactory: add event received"; label2.setStyle("color", 0x00CC00); }

]]
>
</fx:Script>

<s:Label id="label1" text="mxmlContent: add event NOT received" color="0xFF0000"/>
<s:SkinnableContainer elementAdd="elementAddHandler1(event)">
<s:mxmlContent>
<s:Button />
</s:mxmlContent>
</s:SkinnableContainer>

<s:Label id="label2" text="mxmlContentFactory: add event NOT received" color="0xFF0000"/>
<s:SkinnableContainer elementAdd="elementAddHandler2(event)">
<s:mxmlContentFactory>
<s:Button />
</s:mxmlContentFactory>
</s:SkinnableContainer>

</s:Application>

Actual Results:
The label on top of the second SkinnableContainer says it received the add event, but the first label does not. This means that the add event is only received when the SkinnableContainer is using mxmlContentFactory.

Expected Results:
Both labels should be green and say the event has been received.

Workaround (if any):
Subclass SkinnableContainer and add the element handlers on the contentGroup when it is added to the display list. Then redispatch the events.