Preparing Websites with Active Content for Announced Browser Changes

In response to the announced changes to Microsoft Internet Explorer browser, Adobe has recommended a solution you can use to keep your sites performing the way they do now. We know that you want your users to have the best possible experiences on your sites. That is our goal as well.

Some of you may find alternate solutions that you found to work better for you. We welcome your feedback and look forward to an open, continuous conversation with you.

In this particular case, we'd like to explain why we recommend that you use the solution we posted, rather than variations of it that you or others may create. Here's why:

• Consistent with solutions recommended by Microsoft: External JavaScript solutions like ours are recommended by Microsoft, and we developed a solution that is the most likely to work with their future browser versions.
• Efficiency: We wanted to limit our fix to one external JavaScript files for an entire site, rather than one external JavaScript file per <object> tag. This reduces the total number of extra files that you need to manage, and means these files get downloaded once and cached.
• Consistency: We built our solution with consistent naming to give our function a "signature" that visual tools like Dreamweaver can understand and edit in the future.
• A truly "external" solution: We moved data that was once internal to the HTML document into external JavaScript files, as recommended by Microsoft.

With these points in mind, we recommend our solution code provided in Preparing Your Website to Handle the Microsoft Changes to Internet Explorer. We also advise that you stay tuned to the Active Content Developer Center for the "official" solutions.

About the author