Well, my guess as to what's happening is that our cleanup scripts are trying
to remove the SWF from the DOM, which causes IE to do a temporary re-paint
with one overlapping the other, before closing the page.
Maybe you could hide this from being visible by setting all the flash
instances to "visibility:hidden" (don't do display:none, causes problems
with EI callbacks) on page unload.
Like, you could do something like this (since you only care about IE):
var old_onbeforeunload = window.onbeforeunload;
window.onbeforeunload = function(){
$("object").css("visibility","hidden"); // used jquery here to make it
easier
if (typeof old_onunload == "function") return old_onbeforeunload();
};
The line where I used jQuery is nothing special, just a simpler way to
accomplish a goal. Basically you just need to loop through all flash
objects and set their visibility style to hidden, depending on what JS
frameworks/logic you have available to you on the page.
--Kyle
--------------------------------------------------
From: "Jeff L" <[email protected]>
Sent: Monday, June 15, 2009 10:23 AM
To: "SWFObject" <[email protected]>
Subject: Re: strange behavior in IE
>
> You know, I'm not sure. It only seems to happen with that second
> flash. And only when that flash is second on the page. If I switch the
> position of the flash and put that one first, it doesn't seem to
> happen anymore.
>
> Unfortunately, that flash was not developed by us, but rather by an
> outside company. It's also being hosted externally...wonder if that
> could have anything to do with it as well.
>
>
> Just out of curiosity, I went back and tested the last version of
> Bobby's UFO script (3.22) and I don't see the issue with that script,
> however.
>
>
>
> On Jun 15, 9:39 am, Aran Rhee <[email protected]> wrote:
>> Jeff.
>>
>> Thanks for the test page. I'll have a look at this as soon as I can (it
>> is
>> late here in Aus, and I need sleep).
>>
>> re: how often is SWFObject is used to embed multiple Flash files - Well,
>> SWFObject is the #2 javascript library on the net behind jQuery ( ~ 6% of
>> ALL sites on the net), so I should think there would be more than a
>> handful
>> sites with more than 1 swf on the page :)
>>
>> To clarify, are you saying you only notice the bahavior if there is more
>> than 1 swf on the page? This would help narrow down a test case.
>>
>> Cheers,
>> Aran
>>
>> On Mon, Jun 15, 2009 at 11:33 PM, Jeff L <[email protected]> wrote:
>>
>> > Ok, here is a stripped down test page that shows the same behavior.
>>
>> >http://production.danversbank.pixelmedia.net/swfobject-test.html
>>
>> > Easier to see when clicking on the link than reloading the page. The
>> > second flash duplicates itself on top of the first flash movie.
>>
>> > I've moved the script blocks into the head, no difference. No extra
>> > HTML on the page except a link. And I've tested w/ v2.2 locally with
>> > the same behavior.
>>
>> > You said "his behaviour does not happen on all sites either"....how
>> > often is swfobject used to embed more than 1 flash movie into a page?
>>
>> > Jeff
>>
>> > On Jun 15, 8:17 am, Jeff L <[email protected]> wrote:
>> > > Unfortunately, because it's a CMS, they can not be defined in the
>> > > head.
>>
>> > > I am not sure what work has been done to the cleanup functions, but
>> > > it
>> > > looks like the same exact issue that was reported back in 2006 at the
>> > > archive link I posted.
>>
>> > > I will work on starting to strip down the HTML to see if there is
>> > > anything there that is causing the issue.
>>
>> > > I welcome other feedback though, as if I can't find anything else I
>> > > will have no other choice but to comment out the cleanup function.
>>
>> > > Jeff
>>
>> > > On Jun 12, 8:38 pm, Aran Rhee <[email protected]> wrote:
>>
>> > > > Hi Jeff.
>>
>> > > > Yes, there was a lot of work done to fixissues around streaming
>> > > > audio /
>> > FMS
>> > > > not releasing memory and streams so I would not recommend removing
>> > > > any
>> > > > functions / lines related to that.
>>
>> > > > As you say, it happens only in IE.
>>
>> > > > Perhaps other SWFObject contributors who worked on the cleanup
>> > > > function
>> > can
>> > > > shed some light on a more elegant work around, but one thought is
>> > > > to
>> > call a
>> > > > function before you invoke your link which hides the divs
>> > > > containing
>> > flash
>> > > > items. This behaviour does not happen on all sites either, so I am
>> > wondering
>> > > > if there is something specific in your HTML which is causing the
>> > > > shift
>> > in
>> > > > layout...
>>
>> > > > BTW - I noticed your SWFObject script blocks are appearing with the
>> > body
>> > > > tag. These should be defined in the head. Unlike SWFObject 1.x
>> > > > which
>> > ran
>> > > > inline, SWFObject 2.x runs all embed functions etc on ondomready()
>>
>> > > > Cheers,
>> > > > Aran
>>
>> > > > On Sat, Jun 13, 2009 at 4:22 AM, Jeff L <[email protected]>
>> > > > wrote:
>>
>> > > > > Hi folks,
>>
>> > > > > I'm getting some strange behavior in IE. I get this behavior even
>> > with
>> > > > > the new 2.2 version of swfobject.
>>
>> > > > > If you check out this page, scroll to the bottom, there is a
>> > > > > little
>> > > > > flash piece on the bottom right:
>> > > > >http://production.danversbank.pixelmedia.net/
>>
>> > > > > If you click a link on the page, the flash seems to duplicate
>> > > > > itself
>> > > > > for a second before the new page loads.
>>
>> > > > > I've done some research and found this link:
>>
>> >http://lists.deconcept.com/pipermail/swfobject-deconcept.com/2006-Aug...
>>
>> > > > > The problem seems to be similar, although the code has been
>> > rewritten.
>> > > > > I've tracked it down to this function: removeObjectInIE()
>> > > > > (line 494 in v2.2)
>>
>> > > > > In version 2.1, it looked to be just this one line causing the
>> > > > > issue:
>> > > > > obj.parentNode.removeChild(obj);
>>
>> > > > > In version 2.2, it also seems to be caused by this loop:
>> > > > > if (typeof obj[i] == "function") {
>> > > > > obj[i] = null;
>> > > > > }
>>
>> > > > > If I comment the call to that function, the problem goes away.
>> > However
>> > > > > I see a comment in the code:
>> > > > > "Release memory to avoid memory leaks caused by closures, fix
>> > > > > hanging
>> > > > > audio/video threads and force open sockets/NetConnections to
>> > > > > disconnect (Internet Explorer only)"
>>
>> > > > > So I'm wary to comment that line out.
>>
>> > > > > Any help is appreciated!
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SWFObject" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/swfobject?hl=en
-~----------~----~----~----~------~----~------~--~---
