DIGG IT! I have refined my Eolas solution for Flash a bit. Specifically it has now "PASSED" testing with the test version of Internet Exploder.
I would like to stress that this solution might be non-compliant as the changes to IE are not firm and currently represent "beta / alpha" code. The solution was tailored to the language of the proposed changes and not to a hole in the implementation. Here is a snip from Microsoft's site on the subject:
http://msdn.microsoft.com/ieupdate/activexchanges.asp
Affected Web Pages
All Web pages with ActiveX controls are affected by this change unless they meet one of the following conditions.
- The controls are created dynamically from script loaded from another location.
- The controls do not reference remote data.
Avoiding the first case, you can instantiate an OBJECT with minimal information other than the OBJECT tags. Since this doesn't reference remote data initially, the OBJECT doesn't warn the user. Next we modify the OBJECT with JavaScript using the ID that the OBJECT was instantiated with and VIOLA the object is working properly.
The key is determining which items in an OBJECT refer to remote data. Personally I feel several portions of the standard OBJECT tag set violate this rule:
1. CODEBASE="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"
2. PARAM NAME=movie VALUE='mymovie.swf'
Outside of those two URLS, the OBJECT tag is clean. These items are added into the OBJECT with the JavaScript as follows:
window.{ID OF OBJECT}.codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"
window.{ID OF OBJECT}.LoadMovie(0,"sample.swf")
The second tag uses a Flash Player method that has been available since F3 (Version 3 Flash) of the ActiveX control.
Here is a good example:
eolas.zip
Cheers,
ted ;)
0 Responses to “ Eolas Workaround Part 2 ”
Post a Comment