rabies — 2006-09-27T11:54:29-04:00 — #1
So you're here because you find that you have an ugly box around your Flash content when viewing it in Internet Explorer.
Or you find you need to CLICK TWICE to get any Flash to work properly.
History of this problem:
These are a result of Microsoft losing a lawsuit with a company called Eolas. MS decided to not pay for a patent license and instead patched their browser to work in a way that does not infringe on the Eolas patent.
Visit www.Adobe.com and download the "fix" for Flash called "Active Content Update". This fix adds a publishing option, and also a new "Command". You must use this publishing option and use the Command in order to "add" the fix to your HTML page.
Anyone else: Please add relevant links to other solutions, and perhaps to that older thread which discussed this Eolas mess.
rabies — 2010-06-11T23:35:00-04:00 — #2
You're wrong. SWF files usually contain a timeline. It certainly does "play". That's why there is play(); and stop(); as the most basic ActionScript most people learn first.
rbutler — 2006-10-02T12:02:19-04:00 — #3
Abobe's solution in my opinion is quite bulky and ridiculous. The best script I have found so far which works well is at the below address:
stevewebdev2005 — 2006-09-27T12:49:49-04:00 — #4
mhulse — 2006-09-27T13:56:18-04:00 — #5
Anyway, another reason to hate IE. :headbang:
rabies — 2006-10-04T15:41:09-04:00 — #6
PS: If you wish to read up on a variety of other (yet similar) methods to fix this issue, do a SitePoint search for "eolas".
Here's a lengthy thread which much discussion of this issue: http://www.sitepoint.com/forums/showthread.php?t=372542
vidman — 2006-11-15T20:49:17-05:00 — #7
I actually posted this in the 'dhtml display over flash' thread but it applies to here as well and is the best solution to IE's "click to activate" bug I have seen-
====== re post below from another thread ===========
Thanks to a friend at another forum for this tip.
There IS a way to make flash run UNDER dhtml and still avoid IE's "click to activate" feature (ahem!).
See how here- http://blog.deconcept.com/swfobject/
It took a bit of getting my head around how it all works but its not that hard in the end. I had to dig a bit more as my flash is pulling random movies and such but once you figure out how the so.addParam works, it's easy stuff (basically the same as the old way of publishing flash).
See it in action here- http://www.zacspeed.com/exotecsp3.shtml (click on the product images to see the dhtml running OVER the top of the flash header).
There is an extension for Dreamweaver so you use this method with just a few mouse clicks (http://www.communitymx.com/abstract.cfm?cid=3DA1E).
afroninja — 2006-12-12T16:48:03-05:00 — #8
magi — 2006-12-22T18:47:07-05:00 — #9
How it works?
Please, I need help. :injured:
crafter — 2007-02-05T13:29:42-05:00 — #10
I'm definitely suggest to use SWFObject to fix this issue. It's most smart and simple solution and also easily integrating with flash player ExpressInstall.
In the download package you will find few samples of usage.
Also pay attention to the SWFAdress script that intergrated with SWFObject. Very useful for the deep linking in flash sites.
steve100 — 2007-02-13T06:23:20-05:00 — #11
Great - any idea where the zip file is for this?
acquiesce — 2007-02-15T08:01:32-05:00 — #12
If you are using Dreamweaver 8 there is a solution for this included in the 8.0.2 Updater.
To summarise whenever you insert an .swf file into your webpage it will create an external .js file in a subfolder entitled 'Scripts'.
It will also add the same into any existing webpages which include .swf files when you re-open them in DW.
I downloaded the updater the moment I saw it and haven't had any problems since.
rbutler — 2007-02-16T17:10:39-05:00 — #13
There's no zip file. Just download the trial, execute it once, and you'll notice what's going on (it's not difficult). Then uninstall the program.
rbutler — 2007-02-16T17:11:34-05:00 — #14
See if this helps:
rbutler — 2007-02-16T17:12:46-05:00 — #15
That's the same worthless script that has been known to cause conflicts in pages with extensive body calls and JS occuring.
deelunn — 2007-03-14T06:59:37-04:00 — #16
ive been using the SWFObject to fix this issue in ie....however im after a way of making the movies transparent?
any ideas - heres the movie in question
dujmovicv — 2007-03-14T09:41:02-04:00 — #17
uberhost — 2007-07-17T07:36:23-04:00 — #18
Create a file called movie.js, for instance, with the following code (you'll need to edit the size, movie name, Flash version, paths, etc:
document.write('<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,79,0" id="movie" width="300" height="300">\
document.write('<param name="movie" value="movie.swf">\
document.write('<param name="quality" value="high">\
document.write('<param name="wmode" value="transparent">\
document.write('<embed type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" name="header" width="300" height="300" src="movie.swf" quality="high" wmode="transparent" swliveconnect="true" allowscriptaccess="samedomain"></embed>\
Add this between your <head> tags:
Then simply add this code where you'd like your movie to display:
If you're doing it like that, IE7 should have no problems at all, and there should be no "click to activate" problem either.
One thing, it is a sort of validation "cheat" though.
OT: Sorry for the bump, but I thought this info might be useful to someone.
revsorg — 2008-04-23T07:21:23-04:00 — #19
Have you seen this?
'On November 8, 2007, Microsoft announced that, as a result of recent technology licenses acquisitions, the 'click to activate' restrictions are no longer mandatory. Microsoft plans to remove the activation behavior from Internet Explorer in April 2008'
paul_ferrie — 2008-04-23T07:23:42-04:00 — #20
yeah but i hear this is only going to apply to a patch release for Vista.
next page →