google-code-export / swfobject

Automatically exported from code.google.com/p/swfobject
1 stars 1 forks source link

swf loaded twice in Firefox #456

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open Firefox w/Firebug
2. Watch requested files 
3. The swf will show up twice in the list

(this even happens with the demo zip file downloadable from code.google.com.

Firefox 3.6.3 OSX 10.5.8, 
FireFox 3.6.3 Windows XP Professional Service Pack 3 

Original issue reported on code.google.com by tweenors...@gmail.com on 6 Apr 2010 at 8:56

GoogleCodeExporter commented 9 years ago
http://code.google.com/p/swfobject/wiki/faq#16._Why_does_Firefox_load_my_SWF_twi
ce?

Original comment by mail%mar...@gtempaccount.com on 7 Apr 2010 at 11:01

GoogleCodeExporter commented 9 years ago
I read the comment and I read a lot of posts... but still which possible 
workarounds are there? Did anybody get rid of this problem? I have it by myself 
and I freak out... :(

Original comment by phil...@meisen.net on 14 Jul 2010 at 9:05

GoogleCodeExporter commented 9 years ago
AS the FAQ says, this is not a SWFObject direct bug, but Firefox. 

Original comment by aran.rhee@gmail.com on 19 Jul 2010 at 6:06

GoogleCodeExporter commented 9 years ago
Hello all,

I would like to say that in swfObject 1.5 this bug does not appear to exist. 
But in swfObject 2.2 the bug exists.

Regarding the bugs mentioned on FAQ#16, Firefox says they are solved since 
version 3.0.5 and I have Firefox version 3.6.8 .

My question is, who owns the bug? Firefox or swfObject library ?

Thank you in advance,
George.

Original comment by hernes...@gmail.com on 30 Sep 2010 at 4:09

GoogleCodeExporter commented 9 years ago
I am encountering this as well on FF3.6.12 & swfO2.2. 

May not be a swfO issue, but I am sure swfO has many internal workings to 
address different browsers right? So late model FF is now different, so we are 
asking for a work around or fix if possible, even if it is not a swfO problem - 
it's definitely a swfObject Users problem!

Thanks

Paul

Original comment by gishtes...@gmail.com on 3 Nov 2010 at 2:57