Last week we celebrated the Firefox-3 day!
The cities acquired a solemn character, and the streets were flooded with reckless youth.
Ok, I lied, it wasn’t really like that, anyway, the new fox is out.
With so many awesome features I just couln’t resist, However, as you all know, foxes are foxy! shrewd and foxy.
With this information kept in mind, I made the upgarde.
Well, maybe that fox isn’t that foxy after all I thought to my self after seeing my configuration and (almost) all my add-ons seamlessly added.
That’s exactly what the fox wanted me to think.
Today, I noticed that Flex Builder doesn’t stop at breakpoints, “so it is a foxy fox after all” I pondered…
Well, at first I thought this was a local, googled confirmed this was an open bug in JIRA.
This kind of behavior reminded me of when I was using strict firewall rules that prevented the debugger from connecting to the flash player via through port 7935.
However, this wasn’t the problem, the firewall was off.
Since nothing reasonable seemed to help, I tried some weird idea that worked:
I added “wmode” parameter in the index.template.html file, and set its value to “opaque”.
The default value of this parameter is “window”, which means the flash player render timing is controlled by the web browser, when wmode is set to “opaque” the flash object is actually rendered by the operation system. This is actually the reason why in opaque mode the flash objects hides everything behind it.
Honestly I can’t see why the rendering should affect the ability to debug.
I only tested it on WinXP+FB3. I wonder if it behaves the same way on different machines.
Cheers,
Almog.
June 25, 2008 at 2:14 pm
sorry my english is a little bit bad,
In flex builder 3, the index.template.html has no wmode properties by default, for debugging you need to set it opaque or transparent work fine for me as well this “wmode” is set
June 25, 2008 at 2:59 pm
Hi Mathieu,
you’re right, the index.template.html by default do not specify the wmode parameter, and by not doing that, the flash object will behaves as if wmode was set to “window”.
I didn’t try to set wmode to transparent, actually it’s quite surprising to see it works too, however, I wouldn’t go with transparent, because it’s uses mroe system resources to render the swf.
Cheers.
September 2, 2008 at 12:54 pm
What do you mean by working on dirfferent machines, only the OS? I got it run on XP Pro SP3 and it worked fine.
September 16, 2008 at 10:52 am
i had a similar issue (debugging failed completely for Flex projects and partially for AS projects). i am on win xp + FB3.
i disabled AdBlock plus (from tools\add-ons, not from adblock plus’s icon) and now its working.
September 21, 2008 at 11:46 pm
This is a platform independent issue, it is to do with window rendering in the Flash player. The window mode property must be set to work around the described problem, as originally pointed out in the article – index.template.html
Confirmed this same problem will prevail if this is not defined in OS/X leopard. The work around is trivial, simply add the wmode value and your good.
October 24, 2008 at 8:36 am
Hey Almog – Funny to find this issue in your blog (after a new formatted PC this happened in my FF3)
I found out that the wmod did not help me but when i disabled the IE tab extension it worked.
December 7, 2008 at 11:15 am
and then again – is a different case – this did help.
