Update:
Earlier this month the normal Windows Updates introduced the changes to remove "click to activate" for IE.
ieblog.

The "click to activate" certainly seems to have gone, but I notice on Freeola's SWF advert where before clicking twice would make the link work, now for me the link doesn't work at all, other swf links seem to be working fine. 

I don't use Flash, so I'm not sure how you've added the link to your swf file but you might want to take a look at it.

I'm using IE7 and the latest Flash Player (9,0,124,0).


^{Search Freeola Chat}

Thanks for that cjh.

Windows XP SP3 - I thought Vista had killed that off, but it appears not.

I hope it doesn't cause as much trouble as SP2 did!

<sup>BSODS etc.
I can still remember the phone calls...




Search Freeola Chat</sup>

I've recently been adding more flash content to my website, then noticed that after upgrading to IE7, I was receiving the click here to activate message, how annoying!

So I searched around for a script or method of properly embedding the flash object into the page. I stumbled by chance across this 'SWFObject' guide that allows you to not only add flash with javascript, but to ensure that the user automatically updates the browser flash plugin, or installs it on the fly if it doesn't exist, without leaving your site. Very handy!

Here's the information:
http://blog.deconcept.com/swfobject/

I hope you find it as useful as I did...

The "dont use flash" fix is pretty good too. :)

Sorry Eccles, I should have mentioned it was a MS 'feature' in my post. As you mentioned it was introduced a few years back when applying normal Windows Updates.

Which fix are Freeola going to use?
;¬P

Hmmm... wrote:
> Looks like you even found an old AppleMac to try and see an
> error ;¬)

Are you suggesting I own a Mac? No need for insults you know. :(

It was windows Safari I tried.

It doesnt create problems as such.  In fact looking at your page in Firefox not even that reports it.  I really thought it did in the past though (not that I'd trust my memory).
outerHTML is an IE invention (Opera supports it as well), its not available in other browsers.  So technically such code should be wrapped in

if (document.body.outerHTML) {
...
}

But if Firefox isnt reporting any error, doesnt really matter.  So basically, ignore me. :)

Hmmm... wrote:
> objects =
> document.getElementsByTagName("object");
> for (var i = 0; i < objects.length; i++)
> {
> objects[ i].outerHTML = objects[ i].outerHTML;
> }

This should really be wrapped in a check to see if outerHTML is valid, otherwise it creates errors on the page for those browsers that dont support it.