As it appears there’s a problem to implement the mousewheel over a Flex application under Mac. There is a solution, unfortunately through JavaScript, but however it works.
See how on http://blog.pixelbreaker.com/flash/as30-mousewheel-on-mac-os-x/
The problem is that the mousewheel event listener is registered by the JavaScript and sometimes is still working after mouseout from the flash movie.
If someone wanders why the fullscreen doesn’t work correctly under IE, after calling StageDisplayState.FULL_SCREEN in Flex – there’s the answer. Just don’t forget to add
<param name=”allowFullScreen” value=”true”>
parameter of the object tag. You may also set allowFullScreen=”true” of embed tag.
Z-indexes on IE 6 works almost like on any other browser, but if something does not work for you, please do not forget to check (or even double check) the paramter for transparent background of the flash. Not only the z-index, and absolute positioning is needed, just add this line of code in your object tag:
<param name="wmode" value="transparent" />
Why flash does not work correctly with Flash ExternalInterface see here:
How to write object tag to make your IE browser work I’ve written here:
Do not use only ’embed’ tag when using Flex 3/Flash Actionscript 3 ExternalInterface. The communcation with only embed tag works with Firefox and no other browser. If you want to put the IE on work add the ‘object’ tag as well.
Sometimes Flash Player with debugger is no displaying all correctly. I have an application which displays more than 200 bitmaps on the stage. Because of the Flash Player with debugger helping my Flex Builder 3 installation to work/debug properly the application always loaded correctly those bitmaps, but after been reported by several places that the bitmaps were not loading at all I faced the two-day sprint of finding the issue.
Finally I noticed that the issue does not exists for machines with installed Flash Player with debugger. After uninstalling the software from my machine I start having the problem there.
That case showed us that the ‘debugger’ version was ‘suppressing’ the problems sometimes. In our case it was an incorrect class instance.