SWFObject 1.5 released

I’m pleased to announce the next semi-major release of SWFObject (Direct download link). This version has been in development for quite a while, but only because I haven’t been able to find time to update the documentation.

There’s really only one large change to the code, and a few bug fixes I’ll outline here:

Express Install functionality has changed. You no longer need to add any Actionscript to your fla or otherwise modify your project’s files. The new syntax and functionality is outlined on the SWFObject page in the Using Express Install section.
Fixed a bug that was causing IE6 to crash intermittently if users had a certain version of Flash Player 6 installed and the page was refreshed a few times
Added support for IE Mobile devices that have Flash Player installed (more details here)
Added support for style tags on the object/embed tags outputted from SWFObject. This allows it to be used with swfIR without having to include the SWFObject code multiple times.

This also may be the last major release of SWFObject. If you haven’t already heard, the SWFFix project will be attempting to replace SWFObject as the de-facto Flash embedding standard. The project is still in the alpha stage, but is looking quite promising. So until then, enjoy!

258 thoughts on “SWFObject 1.5 released”

Hey guys,

I read a few posts above about the SWFObject now working for Flash Player 9. This happened to me this morning and I couldn’t find a fix anywhere so I dug through the .js file and fixed the problem. Currently when trying to detect the flash plug-in it is using “ShowckwaveFlash.ShockwaveFlash.7″, this works for 8 but not for 9. You have to wrap that entire try/catch with this try/catch:

try{var axo=new ActiveXObject(“ShockwaveFlash.ShockwaveFlash.9″);}catch(e){
// existing try/catch here
}

This goes in the “deconcept.SWFObjectUtil.getPlayerVersion” method. I can post the entire file if it’s cool with the original developer. I’m sure they’re already working on this fix, but to get people by you can use this.

I’m still getting an n has no properties error when trying to use this. I see this was a bug in 1.4.3 and fixed in 1.4.4. Did you reintroduce it?

@Joel
It would be really cool if you could post the entire file…

Thanks a lot!!
Stefan

Looks like Microsoft and IE did it again. Last night’s (2/12/08) windows update killed every Flash version detection algorithm working for IE including SWFObject.

Above is url

Confirmed new IE patch breaks SWFObject.

Maybe best to use a MS documented detection method. These usually maintain forwards compatibility, and although SWFObject is in massive use MS has no responsibility to remain compatible with your code.

http://msdn2.microsoft.com/en-us/library/ms537509(VS.85).aspx

-Ben

Hi, SWFObject doesn’t work with the latest version of IE7. Although it’s good because it forces me to use Firefox more regularly, it’s a real problem because my clients are facing the same issues and they aren’t willing to change browser. Is there a planned fix for this? Otherwise it’s going to be a case of jumping ship and having to replace every instance of SWFObject I’ve used for the past 3 years for something that does work with IE7, which would be a huge shame because I like the product.

This version posted above fixes the IE issue

http://ztlnascar.com/swfobject.js

-Ben

Joel Flint on February 6, 2008 at 3:19 pm said:

Hey guys,

I read a few posts above about the SWFObject now working for Flash Player 9. This happened to me this morning and I couldn’t find a fix anywhere so I dug through the .js file and fixed the problem. Currently when trying to detect the flash plug-in it is using “ShowckwaveFlash.ShockwaveFlash.7″, this works for 8 but not for 9. You have to wrap that entire try/catch with this try/catch:

try{var axo=new ActiveXObject(“ShockwaveFlash.ShockwaveFlash.9″);}catch(e){
// existing try/catch here
}

This goes in the “deconcept.SWFObjectUtil.getPlayerVersion” method. I can post the entire file if it’s cool with the original developer. I’m sure they’re already working on this fix, but to get people by you can use this.

jf
Phillip on February 8, 2008 at 6:31 pm said:

I’m still getting an n has no properties error when trying to use this. I see this was a bug in 1.4.3 and fixed in 1.4.4. Did you reintroduce it?
Stefan Seiterle on February 11, 2008 at 2:26 pm said:

@Joel
It would be really cool if you could post the entire file…

Thanks a lot!!
Stefan
Steve on February 13, 2008 at 7:40 pm said:

Looks like Microsoft and IE did it again. Last night’s (2/12/08) windows update killed every Flash version detection algorithm working for IE including SWFObject.
wheels on February 17, 2008 at 11:30 am said:

Above is url
Mr-Yellow on February 17, 2008 at 8:03 pm said:

Confirmed new IE patch breaks SWFObject.

Maybe best to use a MS documented detection method. These usually maintain forwards compatibility, and although SWFObject is in massive use MS has no responsibility to remain compatible with your code.

http://msdn2.microsoft.com/en-us/library/ms537509(VS.85).aspx

-Ben
Dan on February 21, 2008 at 9:57 am said:

Hi, SWFObject doesn’t work with the latest version of IE7. Although it’s good because it forces me to use Firefox more regularly, it’s a real problem because my clients are facing the same issues and they aren’t willing to change browser. Is there a planned fix for this? Otherwise it’s going to be a case of jumping ship and having to replace every instance of SWFObject I’ve used for the past 3 years for something that does work with IE7, which would be a huge shame because I like the product.
Mr-Yellow on February 24, 2008 at 6:59 pm said:

This version posted above fixes the IE issue

http://ztlnascar.com/swfobject.js

-Ben