Closed GoogleCodeExporter closed 9 years ago
Could you please add a link to a test page?
Original comment by bobbyvandersluis
on 21 May 2009 at 9:12
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
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
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
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
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
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
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
Original issue reported on code.google.com by
chris.de...@gmail.com
on 21 May 2009 at 3:41