Tanny pointed out a serious problem when it comes to JavaScript solution something I’d read about but hadn’t tested properly. Noteworthy is that it won’t work with inline scripts in the web page, only external ones. There’s an article on MSDN, Activating ActiveX Controls, which describes different techniques doing this. If you create the ActiveX object, in most cases this means an object tag, through script, then you will bypass this security warning. “Luckily”, there’s a fix for it, which I guess is because of some kind of glitch in the patent. Naturally, no one wants your Flash movies, videos and the likes to be presented to the end user like that. When hovering the ActiveX element the user is presented with a tool tip text that reads: The gist of the patch is that no interaction with ActiveX elements will be initially allowed until the user has enabled the ActiveX by clicking it or tabbing to it and then pressing spacebar or enter. If you want to test your web pages before that, you can download the patch and install it right now. This dreaded update, named Microsoft Security Advisory (912945), has been available for a couple of months, but on April 11 it will be forced out en masse through Windows Update so we have a few days till all hell breaks loose. Due to the patent case with Eolas, Microsoft has been forced to update how ActiveX components behave in web pages. On the contrary, the implications of this are huge and will most likely affect a lot of web sites. An alternative solution to this problem is my FlashReplace library.Īlthough news of this has been around for a while, many people seem to have missed it and/or didn’t think it was worth reading up on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |