[FLEX-28011] UncaughtErrorEvents not dispatching for SWF loaded via SWFLoader

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK 4.1 (Release)
• Component/s: mx: SWFLoader
• Environment: Affected OS(s): All OS Platforms; Affected OS(s): All OS Platforms; Browser: Other (specify version); Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 02/Aug/11 06:21
• Updated: 02/Aug/11 06:25

Description

Steps to reproduce:
1. Create A.swf and B.swf Flex Applications (100% MX component based) linking the SDK libraries via RSL for both.
2. In A.swf use SWFLoader to load B.swf SubApplication.
3. Attach listener to A.swf's loaderInfo UncaughtErrorEvents.
4. Load B.swf and attach UncaughtErrorEvents listener to B.swf's loaderInfo and SWFLoader's FlexLoader.uncaughtErrorEvents.
5. Produce an uncaught error in B.swf

Actual Results:
Neither the of the loaderInfo.uncaughtErrorEvents for A.swf or B.swf dispatch an event. Instead the default flash error console appears without a chance to handle the event.

Expected Results:
According to AsDoc (http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/events/UncaughtErrorEvent.html) the event should dispatch through the loaderInfo hierarchy in the following sequence:

1. (Capture phase) A.swf's LoaderInfo
2. (Capture phase) Loader in A.swf
3. (Target phase) B.swf's LoaderInfo
4. (Bubble phase) Loader in A.swf
5. (Bubble phase) A.swf's LoaderInfo

Workaround (if any):

1. Build A.swf and B.swf MX Flex Applications with the SDK libraries merged into code so they both have a copy of the library classes. This works as expected/documented.

OR

2. Build A.swf and B.swf Flex Applications with 100% SPARK based components and you can keep the SDK libraries linked via RSL. This works as expected/documented.