Hi Alex,
I believe I'm having a problem similar to Brian's: FABridge working in FB3 and
not in FB4. File FABridge.js accesses the DOM like this:
var flashInstances = document.getElementsByTagName(embed)
and returns an empty array in FB4. Obviously, with no flashInstance, FABridge
In my copy of FABridge.js, it also scans the “object” tags which in theory
should find SWFObject. Although in Brian’s case, I just realized that
“document” might be the wrong document and that needs to be verified.
I didn’t realize there as an FB4 option for generating FABridge templates. Do
Alex,
I thank you for your patience. However, in one of my earlier posts on this
thread I did give quite a lot of details about my particular situation
(which is almost certainly different, but at the same time, related to, the
other posters issue).
In my case, I'm using an IFrame component
Brian,
Thanks for the additional info, but what I am really asking for is unambigious
language about what your debugging has discovered so far. If you are using
parent.FABridge on the JS side, what does parent point to? Is it what you
expect? If you place breakpoints on the AS side, do you
Alex,
I think thats (the swfobject) probably getting pretty close to the right
line of thinking, and its something that I'd considered briefly myself, but
I am not savvy enough yet to make heads or tails of the issue.
--
Brian J. Ackermann
brian.ackerm...@gmail.com
Yes, I've tried debugging on the JS side of things, exactly as you mentioned
(See my email in this thread from Thu, Aug 26, 2010 at 12:45 PM). Nothing.
I simply can't find the object. I used a javascript object dump function,
to 'scan' the objects I could think of, looking for an occurrence of
So from my perspective, you aren’t being specific enough. You are saying that
parent.FABridge doesn’t exist, the OP said something else. There are two DOMs,
the JS DOM and the AS DOM. You are now saying you can’t find the object, but
you aren’t saying which object.
If parent.FABridge is
Hi,
Was this problem resolved? I have Flex 3 MXML that defines:
mx:Application
...
utils:FABridge bridgeName=foo/
...
/mx:Application
In Flex 4, must this statement now appear inside an fx:Declarations element?
Even if there's no other fx namespace elements being used in the MXML?
I don’t have time to try it right now. In Flex 4, the tag goes inside the
fx:Declarations tag. I took a quick look at the AS code and it uses
ExternalInterface so it shouldn’t be sensitive to changes between Flex 3 and 4.
Have you tried debugging from both sides? Use a JS debugger or stick a
9 matches
Mail list logo
