Recently, Microsoft changed the way Flash and anything else that uses <object>, <embed>, or the <applet> method of accessing ActiveX controls. This is a result of the Eolas versus Microsoft patent case regarding the way Microsoft was accessing the ActiveX controls to handle those tags. On February 28th, Microsoft released a patch which changed the way Internet Explorer works with ActiveX.
I paid attention to this case closely. I don’t do the Flash work around here, but I do implement it on many of our sites, so I wanted to be sure we had our bases covered.
Last year, RD2 Best Practices called for the use of the Satay Method for including valid Flash objects in a web site. Unfortunately, using this method triggers the patch and the new “click or hit spacebar for activation” comes up.
In a recent update to our Best Practices, we switched to the use of Unobtrusive Flash Objects, or “UFO”, as our method of implementing Flash.
How exactly does using UFO solve this wonderful problem? Through plain old trickery, my friends.
Since UFO works dynamically, it falls under Microsoft’s preferred method for fixing your ActiveX controls, which basically says that any ActiveX controls dynamically written to the screen are automatically activated for user interaction.
No grey borders, no “click or hit spacebar for activation” — just Flash working properly.