Tony said the following on 11/1/2006 12:19 AM:
Here's what I actually found out from doing my research today...
Did your research also turn up any references to quoting what you are
replying to?
First off, the ActiveX content blocker happens when you have an
external javascript file on your hard drive that your html page is
referencing.
Non-sense. Whether it is external or not is irrelevant. Put an empty
script element in a page that is set to default settings and test the
page. You will still get the Active Content warning. (It's an Active
Content, not an ActiveX content warning).
So once you place the files on a server then you dont'
have to worry about that part of the blocking.
Search for "The Mark Of The Web" and you can even stop that.
What I did find out is that it also blocks anything with an "on" event
such as onclick onmouseover and so forth.
Reference? I have never even heard of that.
There really is no way to get around the content blocker when the files
are on your hard drive and they include a call to a javascript file.
Nonsense. Research Mark Of The Web. It's trivial. What it *does* do when
you use the MOTW is put you in the Internet Zone so that you can't
reference anything on the Hard Drive.