( Sometime I'll clean out the code and post an example, but for now we're going to concentrate more on the problems encountered when using this solution. )
As I said, the solution is great and works in most situations however, this doesn’t work in the CMS we're using and I couldn’t figure out why. It turns that our problem was;
DOM Access.Net pages put all the html inside a form and apparently this means that objects like embedded swfs become hidden from the Document Object Model in Internet Explorer.
The solution to this is to “elevate” the object to be part of the window rather that the document. It seems that by creating a reference and using a different element in the heirarchy fixes DOM visibility issues. i.e.
window.objectID = document.getElementById(objectID);A strange solution, huh? Ben Waldron has more information on this solution here.