MS modifies IE's handling of ActiveX-objects

because of Eolas. Code has to be changed

[RonPK]

Well, here it is: [msdn.microsoft.com...]

In future versions of IE, inlcuding patches and SPs, users will be prompted each time an ActiveX-object (like a Flash movie) is being loaded. The best workaround seems to be use script to write the <object>-tag.

[Slade]

An article about the above:
[eweek.com...]

[bird]

The best workaround seems to be use script to write the <object>-tag.

The crucial point is not just to use a script, but that the script gets loaded from a seperate file. It must not be embedded on the HTML page. In practise, that script file only needs to contain is this:

function docwrite(t){
document.write(t);
}

Then you can keep the HTML snippet on the page, and just pipe it through the docwrite function instead of having it standing there unadorned (blue is what you would normally write, red is what you'll have to add after (and if) this change gets implemented):

<script type="text/javascript">
docwrite('<object classid="clsid:..."
<param name="..." value="..." />
...
<embed src="...">...</embed>
</object>'
</script>

[RonPK]

Two things strike me as interesting:

1. Eolas objected to MS using Eolas' technology for embedding dynamic, interactive objects in web pages. Now, MS seems to think that by using the script-workaround things should be fine. I don't see any major difference.

2. MS provides a test browser to for developers. Download it, extract to a folder, and "Inside that folder will be a local copy of IEXPLORE.EXE. Double click on that program to run the updated version. Other ways of starting Internet Explorer will run your current system version of Internet Explorer."
So now there is a stand alone version of IE 6 - something many people have been asking for... ;)

[bird]

MS seems to think that by using the script-workaround things should be fine.

That is probably a consequence of the wording of the patent. The disputed "method" is about embedding other applications through a mechanism "within the same document". By moving the mechanism to a seperate JavaScript file, it seems to be possible to circumvent the patent claims.

So now there is a stand alone version of IE 6 - something many people have been asking for.

I doubt that this really is a "stand alone version" in the true meaning of the word. It's just a frontend that patches this specific functionality, but relies on the same DLLs as the standard one otherwise.

[RonPK]

Thanks bird, that's all pretty sensible.

[Jobarr]

"So now there is a stand alone version of IE 6 - something many people have been asking for... ;) "

I saw this too and tested some stuff....and got stand alone versions of IE 4, 5, and 5.5 running on my XP install now! :)

[webmasterworld.com...]

[bird]

That sounds extremely cool, Jobarr!

It also proves my doubts wrong, as you seem to have found a way to really run a self-contained version.