Object Patent Magic

[Kevin Newman]

Hey guys,

What do you think of this:

http://www.unfocus.com/projects/PatentMagic/
http://www.unfocus.com/projects/Pate...PatentMagic.js

This hack just hides the objects, until the page is finished loading,
then replaces them with themselves to get around the recent IE patent
patches.

It's basically a brute force patch for existing pages that embed so
called "active content" in static html.

While it works as it is, it would be nice if I could prevent the first
object (the one that gets replaced) from starting to load, or at least
sandbox it, so that scripts will not get run twice. Does any one know if
that is possible?

Thanks,

Kevin N.

[Randy Webb]

Kevin Newman said the following on 4/21/2006 12:13 PM:

Hey guys,

What do you think of this:

http://www.unfocus.com/projects/PatentMagic/
http://www.unfocus.com/projects/Pate...PatentMagic.js

This hack just hides the objects, until the page is finished loading,
then replaces them with themselves to get around the recent IE patent
patches.

It's basically a brute force patch for existing pages that embed so
called "active content" in static html.

While it works as it is, it would be nice if I could prevent the first
object (the one that gets replaced) from starting to load, or at least
sandbox it, so that scripts will not get run twice. Does any one know if
that is possible?

document.write your applet code.

Why reinvent the wheel or make it harder than it is?

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Kevin Newman]

Randy Webb wrote:

Kevin Newman said the following on 4/21/2006 12:13 PM:

Hey guys,

What do you think of this:

http://www.unfocus.com/projects/PatentMagic/
http://www.unfocus.com/projects/Pate...PatentMagic.js

This hack just hides the objects, until the page is finished loading,
then replaces them with themselves to get around the recent IE patent
patches.

It's basically a brute force patch for existing pages that embed so
called "active content" in static html.

While it works as it is, it would be nice if I could prevent the first
object (the one that gets replaced) from starting to load, or at least
sandbox it, so that scripts will not get run twice. Does any one know
if that is possible?

document.write your applet code.

Why reinvent the wheel or make it harder than it is?

I agree, and that's what I usually do (it allows for plugin/activex
detection, and dynamic flashvars setting that way anyway). I really did
this just to see if I could. :-)

I also figure this might be useful as a quick temporary fix for someone
who has run into this "click to activate" problem.

Kevin N.

[Kevin Newman]

Kevin Newman wrote:

Hey guys,

What do you think of this:

http://www.unfocus.com/projects/PatentMagic/
http://www.unfocus.com/projects/Pate...PatentMagic.js

This hack just hides the objects, until the page is finished loading,
then replaces them with themselves to get around the recent IE patent
patches.

It's basically a brute force patch for existing pages that embed so
called "active content" in static html.

While it works as it is, it would be nice if I could prevent the first
object (the one that gets replaced) from starting to load, or at least
sandbox it, so that scripts will not get run twice. Does any one know if
that is possible?

Thanks,

Kevin N.

Is there a way to detect when a specific tag is entered into the dom
tree as the html is being parsed in IE? Or is there a way to detect when
a new ActiveXObject has been created in IE?

That would be useful, because then I could just detect when the object
is added in, and replace it before it gets a chance to run.

Thanks,

Kevin N.