"Eolas" IE Patch and Web Client

Hello again,

as most of you probably already know, Microsoft issued a patch for Internet Explorer that modifies the behavior of all interactive ActiveX controls in a web page
http://support.microsoft.com/kb/912945

For those who do not know, before you can interact with an ActiveX in a web page you now have to click on it to "activate" it.

There is a "compatibility patch" that disables this, but it's time limited and will expire at the end of June, so that's not a solution for us.

This impacts the "view clip" functionality in MediaBin Web Client (including in version 4.5.3). As there are workarounds, I was wondering if Interwoven is planning to publish a patch for this issue.

Folco

Find more posts tagged with

Comments

Migrateduser

We examined the documentation before the patch was issued and it appeared its side effects were minimal. When a video or audio clip is loaded by the web page, we already immediately played it. Therefore, the user is not required to interact with the controls. If the user chooses to do so, a tool tip will appear that says "Click to activate and use this control." For example if the user wants to pause play, one extra click of the mouse is required. I just verified that is the behavior observed on XP, which I'm running on my desktop.

Are you observing something different? If so, what are you seeing and what is the configuration of IE?

Migrateduser

No, we're not observing anything different.

In my book, it's also "minor", but I wanted to know from an official source if there was a patch coming to take care of that.

This way, I know what to answer if someone comes screaming at me Smiley Very Happy

Thanks.

Migrateduser

There's no patch coming... of course you could request one through Support. The 4.5.3 codebase was complete and in testing when the details of the IE patch became known to us. It was decided the impact was not severe enough to fix at that time.
It is on a list of items to be addressed in the next release. From the Microsoft documentation it looks like a component can be always enabled if the embedded object tag is inserted into the DOM via javascript.
This solution seems to be counter to security if it's so easy to get around.