[FLEX-26248] Flex 4 ModuleLoader bugs module creation cycle when added as element after module load is ready

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: Adobe Flex SDK 4.1 (Release)
• Component/s: Modules
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Browser: Firefox 3.x; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 14/Dec/10 13:31
• Updated: 09/Feb/11 18:57
• Resolved: 09/Feb/11 16:22

Description

Steps to reproduce:
1. Start the attached example
2. Press V1 button to addElement the ModuleLoader and load the module. Check the creation order events in the text area - this is the correct one.
3. Restart the application
4. Press V2 button to load the module
5. Press V2 to addElement the ModuleLoader and check the creation order events in the text area - here we have wrong order.

Actual Results:

When the ModuleLoader is addElement after the module load is ready, the order of the creation events of the module and it's elements is wrong.

Expected Results:

The order of the creation events of the module and it's elements to be correct.

Workaround (if any): set the module's creationPolicy="none", and create the deferred content after addElement the moduleLoader.