Closed GoogleCodeExporter closed 9 years ago
This is likely caused by another JS library within the page aggressively
removing
elements that are created and managed by SWFObject. SWFObject 2.2 (still in
early
alpha) will offer a solution for this, for now the easiest solution for your
web page
will be to add a test inside swfobject.js just before the J.parentNode call to
see if
it exists (if (J.parentNode){...}), or ensure that the external library does not
remove elements generated by SWFObject.
Original comment by bobbyvandersluis
on 23 Feb 2009 at 9:44
Original comment by bobbyvandersluis
on 23 Feb 2009 at 9:44
Original issue reported on code.google.com by
drain...@gmail.com
on 23 Feb 2009 at 2:56