As mentioned in the FP bug, I am actually able to see this problem from time to time while on some sites, like ajaxian.com, when just clicking on links to other pages/sites. I believe I heard at one time they were using SWFObject when they had flash on their site, but I've not confirmed that for myself, and it doesn't appear to be happening anymore when I visit ajaxian.
It does always seem to be related to the unload of the page when a SWF was on the page, and seems to be related to if there are multiple "onunload" type handlers that may be racing to try and unload/clear out a SWF dom object. Anyway, if there's good reasons not to have the type property in there, we should just leave things as they are. Really, Adobe should fix the bug, but I was just thinking maybe it'd be a helpful interim patch if useful. Perhaps that was just a little too much wishful thinking on my part! --Kyle From: Geoff Stearns Sent: Wednesday, January 21, 2009 1:25 PM To: [email protected] Subject: Re: possible addition for swfobject 2.2 Yeah, if there's not actually a bug/problem then why change it? Can anyone reproduce the issue in the link above while using SWFObject? On Wed, Jan 21, 2009 at 5:36 AM, Bobby <[email protected]> wrote: We're already using the type="application/x-shockwave-flash" for all non IE browsers, it should _not_ be used for IE, because we don't want to mix it with a classid. Any way, I have never seen a report like this for SWFObject and I never saw it popping up myself. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
<<inline: Emoticon1.gif>>
