In my previous post I thought that swfobject was causing the wmode=transparent problem in IE. However, I was wrong. Folkert told me that swfobject only passes the parameter to the Flash Player, swfobject is only the messenger.
Instead of wmode=transparent I also tried wmode=opaque as Jorrit suggested, but it didn’t make a difference. I set up three wmode sample pages to test the issue:
When you’re viewing the transparent and the opaque page in Internet Explorer you can see that editing the walls is quite difficult. You can also see that panning the design results in a strange elastic movement. I hope to find a solution soon….
Update
I’ve been reading this post and it looks like it’s something we have to live with…
SWFs using wmode actually perform slightly different from SWFs that have a default wmode. The difference is that when you are running as transparent or opaque, events are delayed until an onEnterFrame. If you are running at a slow frame rate and drive your movie with setInterval or use any number of other events, you are back to your slow frame rate. The real kicker is that SWFs in IE have this bug. SWFs in Firefox are just fine.
Tim Knip's profile
August 29th, 2008 at 7:06 am
keep in mind that any other setting then “window” will break any input fields you have. this is an unsolved flash bug and will cause your input textfield to have a wrong mapping.
see here:
http://blog.headlondon.com/2006/06/02/no-wmode-please-were-british/
August 31st, 2008 at 11:27 am
Hi Lars, Thanks for the tip. Every now and then Wwe run into these unsolved Flash bugs, developing the Floorplanner apps. Usually we find a way to work around them, but this one seems unsolvable…