Forum Moderators: open
On Windows XP with IE6 and Norton Internet Security, default security settings result in ActiveX Alerts whenever "the web page you are trying to view contains an ActiveX control."
I've always assumed that ActiveX inevitably accompanies Flash, so, if there's a Flash animation on your page, those with default security settings will get an Alert with the warning message and a Norton "Block Once"/"Permit Once" dialogue box.
I've noticed, though, that not all pages I've seen with Flash animations produce this message. What can be done in setting up the Flash to avoid it?
Also, I understand MS is changing the way IE is handling ActiveX controls, so this may complicate what I'm asking. I'm a complete newbie when it comes to Flash and ActiveX, and I won't be handling the implementation, but I need to know enough to advise on whether this can be fixed.
its a bit of javascript that re-writes the object tags on the html page for you.
Also search for "MS Activex" on this forum, there are many threads about this patch and workaround.
mcm
Also search for "MS Activex" on this forum, there are many threads about this patch and workaround.
oxbaker - Thanks. I don't think that what I'm looking for relates to the new MS patch, but I'm not sure. What I'm talking about is, I believe, a Norton Internet Security issue, whose behavior I've described. It could perhaps also be fixed by the new patch, but it goes back to way before the current change in IE... probably to when SP2 was introduced.
What's confusing is that I see Flash running on some pages without this "The web page you are trying to view contains an ActiveX control" message, and on some the message comes up before it will run.
In any event, I'm not talking about the "Click to activate and use this control" pop-up that I understand can result from the recent IE change.
[blog.deconcept.com...]
You put your non-Flash content in the HTML (good for getting crawled by search engines) inside a <div> tag, then SWFObject replaces the whole lot with a browser-specific call to Flash that does not have the ActiveX problem.
SWFObject...
jay5r - Thanks. I'm not a Flash programmer, but I read through the SWFObject page and it looks like it has numerous advantages. I will pass it on to the developers I'm working with.
Do you happen to know, though, what it is in the default Macromedia embed code that triggers the Norton message, and how SWFObject avoids that? (Sorry if it's completely obvious to a programmer, but I don't understand the mechanism that enables SWFObject to work and the Macromedia method to set off alarms).
Here is a breakdown of what the code does:<div id="flashcontent">[...]</div>
Prepare an HTML element that will hold our Flash movie. The content placed in the 'holder' element will be replaced by the Flash content, so users with the Flash plug-in installed will never see the content inside this element. This feature has the added bonus of letting search engines index your alternate content.
Seems to me this would be better done by <noscript>... perhaps less likely to be regarded as spam... though I wouldn't recommend "alternate content" that isn't actually contained in the Flash content.
I'm not sure that even if it is contained, this use of the <noscript> would be wise... as <noscript> isn't an alt tag.
Thoughts?
