I just updated an application to use SWFObject 2.0 yesterday. Hopefully when it gets to QA I won't get bombarded by failed browser issues. If so, I'll just switch, so not to big of a deal.
Although, trying to remember, I've used SWFObject in a quite a few apps that use ExternalInterface/JS in the past and only had to loop through the dom to deal with IE,. Is it something internal to JQuery that was killing IE? Or.... B. On Tue, Apr 22, 2008 at 11:02 AM, Cutter (Flex Related) < [EMAIL PROTECTED]> wrote: > We switched over to SWFObject (then FlashObject) when the EOLAS patent > stuff first came out, and it worked fantastic. Until we began to use > JQuery. Some things were fine, but any page that had a flash object, > renedered via SWFObject, would not be able to use any functions of > JQuery. Wait, let me fix that statement: would not be able to use any > functions of JQuery **in Internet Explorer** (go figure). We saw > something similar with a legacy SWFObject call interfering with us using > Ext on the same page. This took a little time to discover, and even > longer to figure out, but basically SWFObject breaks the DOM in IE. We > found that this wasn't an issue when we used the js that Flash bundles > in when you compile your Flash movie, so we wrote a wrapper and started > using that instead. It's worked flawlessly ever since. > > Steve "Cutter" Blades > Adobe Certified Professional > Advanced Macromedia ColdFusion MX 7 Developer > _____________________________ > http://blog.cutterscrossing.com > > >
