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.
