I don’t have time right now to look and I don’t deal much with FABridge, but are you now saying that parent.FABridge is now the issue? The OP said it was FABridge.flex. Is this on the JS side or AS side? In Flex 4, a child component’s parent is not the main app, they get shoveled down into the skin. It think the document or parentDocument properties or FlexGlobals.topLevelApplication can access the main app.
On 8/26/10 9:10 AM, "Brian J. Ackermann" <brian.ackerm...@gmail.com> wrote: I'm trying to get the IFrameCommTest example (from http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the IFrame itself works, the communication does not. In particular, I need to get the included HTML page to call functions from the flex app (I already have a way to get the Flex app to talk to the HTML). I've exported the project to facilitate your help.http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp The problem, is that the "parent.FABridge" doesn't exist. My guess is that something in flex4 changed with regard to how things are located in the DOM. (This post is directly related to the original. I just thought this would be a clearer example of the problem. ) Thanks, ________________________________ Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 ________________________________ -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
