I actually think that the problem was that Adobe was too quick to respond. They've had a solution up since the first round of worry hit this forum. But I think it was so long ago that most forgot about it. Then when it hit the press again they didn't remind people firmly enough. They treated like the old news it was. Rather than the new news that most still think it is. Bill Lane
> Related question: Do you see reasons why so much of this conversation > about ActiveX changes in the Microsoft browser has avoided the source > material on the Adobe site? Andrew Lucking wrote: Good question. My perception is that this time around Adobe was slower to get *solutions* available. For whatever reasons it was only late last week that I was able to point folks to some workaround samples from Adobe. With the browser update already circulating as an optional download and rumours of it being included in this week's security patch from MS maybe folks started without Adobe's guidance? _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
