paul.bakaus's dashboard

If someone else has the same issue, after countless hours of debugging and a lot of great assistance from Scott (thanks!), I was finally able to spot the issue:

body { display: table; }

This single line causes constant refreshes on the Flash after any DOM manipulation, it is a nightmare to debug and work with. Hope this helps!

Thanks Scott, unfortunately nothing helped :/ I prepared a demo for you and sent it via email - here's an excerpt of the mail for history purposes in this thread:

I now debugged even more and confirmed that it was none of the obvious or not so obvious issues - overflow hidden
isn't being set, the embed container is always visible, and I additionally set its z-index to a high value.

Additional details: Open in Firefox 3.5 and watch for an error in Firebug. It will use createSound three times within the
onload handler, then wait until some JSON calls are done and then, the first call *always* fails (or in some other setups
the first play call when you hit the "Start/Continue" button). I tried to disabled literally everything that was happening
during the onload handler and the rest, but didn't change anything.

Hi Scott,

thanks a lot for the quick feedback! _s is definitely undefined everywhere else, and the soundManager is starting up normally, all with onload etc.

I've also checked if there is any chance the Flash is reloading - at least, it is definitely not happening by rewriting innerHTML or something. However, I recall some alpha users had issues when a jQuery UI overlay popped up - afterwards, all sound was broken. Might this be related to overflow hidden? And why would overflow hidden cause a refresh in Flash?

In the meantime, I was curious and tried three different flash/sound bridges, including jPlayer and Niftyplayer. Funny enough, all of them share the exact same issue. At some point in time during the app, the actual Object looses all its Flash methods (on the DOM node).

I'm going to debug a bit more and try to see if the node that does not work is actually the same than the first node, or if it has been rewritten to some reason. I'll also prepare a demo space for you to look at, maybe you find something I couldn't!

Again, thanks a lot for the insight, talk to you soon with more infos!

Cheers,
Paul

Actually, I was reacting too early :/ It was looking good, but it seems to have been a coincidence. It is still happening with timeouts, although sometimes it fixes or delays the issue. Having a timeout greater than 0 is really no option, which means we seem to need to refrain to another plugin if we can't find a solution asap :/

Scott, if you have any additional ideas (this *only* concerns Firefox as it seems), please let me know!

Thanks,
Paul

In fact we were having a similar issue for a long time and couldn't figure it out - all of the mentioned things we did, nothing helped. Guess what, it was a stack/focus issue!

Simply wrapping the createSound calls that happen directly with some other crazy DOM and focus action with setTimeout(function() {}, 0); solved the hole issue. Arguably it's not beautiful, but I couldn't figure out another way.

Another note: It was only happening on Firefox!