Closed GoogleCodeExporter closed 9 years ago
Highslide probably aggressively cleans the DOM, and removes a node that
SWFObject
adds and wants to remove, while it shouldn't remove it. Who's to blame?
Highslide for
demolishing the DOM for SWFObject or SWFObject for lacking a non obvious feature
test? Best thing to do is to manually add the test if J.parentNode is available.
For SWFObject 2.2 we will use a different method to simulate domload in IE, so
here
this issue would be solved.
Original comment by bobbyvandersluis
on 26 Jan 2009 at 12:16
Original issue reported on code.google.com by
p.debek...@gmail.com
on 26 Jan 2009 at 11:09