As Microsoft (MS) rolled out an Internet Explorer update (KB912812) months ago, you might notice that websites which uses Macromedia Flash or those which uses ActiveX controls now show a bounding box around them and on mouse-over, asks users to click on the content to activate it before you actually get to interact with the ActiveX control. This modification comes as part of an ongoing patent dispute with Eolas Technology and the University of California.
How does it affect IE 6 and Websites: The update changes how it handles active content viewed in certain Adobe products, including Macromedia Flash Player, Authorware Player, Shockwave Player, SVG Viewer, Help Center and Adobe Reader, as well as Sun Java, Apple QuickTime, RealNetworks, RealPlayer and other ActiveX controls. Active content that is embedded in HTML pages in certain ways may not be able to receive user input (for example, keyboard or mouse events) until the user clicks to either activate or continue loading the control.
Recommendations:
Solution 1: Revert back to previous version of IE6 with a Hotfix published by MS themselves. However, this is a temporary fix as MS rolled out the fix for enterprise users to have enough time to prepare their sites for the changes and make sure that all deployed applications which interact with IE can be tested and be recoded to the new way IE handles ActiveX controls. The hofix is only valid till this month as MS would permanently impose the changes soon after. The hotfix can be found here: http://support.microsoft.com/default.aspx/kb/917425.
Solution 2: If you are developing a website, remove the user activation requirement for active content. Developers need to go back and review all their websites which use ActiveX controls and modify and create an external the script to automatically turn on such function. Microsoft provides a guide into activating ActiveX automatically: http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/overview/activating_activex.asp Adobe/Macromedia also provides a JavaScript Fix on their website and an explanation why one should use the Adobe Solution: http://www.adobe.com/devnet/activecontent/articles/devletter.html http://www.adobe.com/devnet/activecontent/articles/why_adobe.html
And My Concern
This whole thing is currently messing up our deployed websites which uses Flash. The first time our IT rolled out the update, some of out flash content went invisible. We had to change some navigation elements on some websites and recode them again. Even then, we still got the "Press SPACEBAR or ENTER to activate" tab on these elements. We got to solving this by using the methods above but since we have about 40+ items we need to fix, we're slowly doing the upgrade as we also need to test everything again. This is ok for websites as we know we have a fix but for third party applications which we use ActiveX, Java and IE, it poses a big headache for us. Either the software maker comes up with a license agreement with Eolas or go back to their code and o the changes. A sample of this is our EDMS (Electronic Document Management System), Filenet IDM web interface. We now have to click twice for each tab that pops up. Talk about minimizing user clicks! And the thing is, the local vendor says it's the first time that they encountered this on Filenet. We're trying to get hold of a username and password to get access to the FileNet's support center. Hopefully, we'd find a way to get this thing solved or else, I'd die clicking away as I update about a 100+ documents and files which I need to upload on EDMS. Argghhh!!!