fullcatrooms / swfobject

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

2.2 beta 1 causes very slow dom ready jquery in IE 8 #313

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use jQuery dom ready
2. Use swf object 2.2 beta 1
3.

What is the expected output? What do you see instead?

Very slow response of dom ready

Original issue reported on code.google.com by chris.de...@gmail.com on 21 May 2009 at 3:41

GoogleCodeExporter commented 9 years ago
Could you please add a link to a test page?

Original comment by bobbyvandersluis on 21 May 2009 at 9:12

GoogleCodeExporter commented 9 years ago
The reason I'm asking is that SWFObject should be called directly and not on dom
ready (by jQuery), because SWFObject itself includes on dom ready, which is 
probably
your case.

Original comment by bobbyvandersluis on 22 May 2009 at 8:22

GoogleCodeExporter commented 9 years ago
Actually the SWF Object calls are outside dom ready... it effects the other 
elements,
especially login panel: 

http://www.mech7.net/tmp/tnt/2009/html/

With old version it works ok..

Original comment by chris.de...@gmail.com on 22 May 2009 at 11:00

GoogleCodeExporter commented 9 years ago
In what browsers/OS did you find this behavior? Which exact elements are 
affected Flash.

Please note that your implementation uses quite a lot of JavaScript and that 
your
SWFObject embed code is at the end of it all, what if you move your calls to the
beginning of your script?

Original comment by bobbyvandersluis on 26 May 2009 at 10:02

GoogleCodeExporter commented 9 years ago
Am not sure I can try to move the code.. but with the old version it does work 
fast..
I tested on IE 8 on XP on localhost... on my host it's kinda slow for me here.

Hiding the login panel on top is much more slow if I use the beta swfObject. On
Firefox it is quick though...

Original comment by chris.de...@gmail.com on 26 May 2009 at 10:16

GoogleCodeExporter commented 9 years ago
Your assumptions are incorrect.

I just setup two test cases:
- both with a jQuery test app
- one with SWFObject 2.1 dynamic publishing
- the other with SWFObject 2.2 beta dynamic publishing
- for both I timed the actual time needed to finish the embed process in 
milliseconds

In IE8 on Win XP with SP2 SWFObject 2.2 performed as desired and actually 
proved to
be faster than the deferred script workaround as used in SWFObject 2.1.

So I'm not convinced that your issue is SWFObject related.

Original comment by bobbyvandersluis on 28 May 2009 at 2:27

GoogleCodeExporter commented 9 years ago
And to be complete, I also timed jQuery's dom ready. The results were around 
the same
for both test cases and not affected by my Flash app that was embedded by 
SWFObject.

Original comment by bobbyvandersluis on 28 May 2009 at 2:59

GoogleCodeExporter commented 9 years ago
How did you check the time? Because to be honest I am not sure how to use a 
profiler
in JS... but only that i can see a big lag in the hiding of the login panel. 

Original comment by chris.de...@gmail.com on 29 May 2009 at 1:48

GoogleCodeExporter commented 9 years ago
You can use: new Date.getTime()

And measure it:
- in the head of your html file before you insert all other scripts
- when the jQuery ready event fires
- when the swfobject addDomLoadEvent event fires

Original comment by bobbyvandersluis on 29 May 2009 at 9:00