Having a problem where slides dont slide in, just out in Firefox. Other weirdness, which I cant figure out the rules to. If I set a speed then the slide just blinks out not slides, etc

Hello Howard.

Can you please provide me with link to the problem page?

Regards:Vulcho.

shortcreative.com/proto/pages/photography.html

its very much a work in progress.


I seem to be able to fix it by adding one additional element, even if there is nothing in it, like this page that works fine

shortcreative.com/proto/pages/real-estate-photography.html

Hello Howard.

Can you try to change transition speeds ?
Change Slide duration: 5000~4000
Change effect duration: 800~500

Regards:Vulcho.

Tried that, changing the timing on the master as well as individual slides. Still getting random speeds in Firefox and Chrome, safari is fine.

Hello Howard.

Can you please send me the page with the slider and the pictures at my e-mail:

Regards:Vulcho.

Are you kidding?

The source files are all online and you have the link, grab what you need.
What I need to know is why the slider timing messes up in Firefox (Mac).
It is a repeatable bug not a problem with just one of my pages.

A brand new page with no change to the code that DMX slider creates the slides just wink in rather than slide in.
Here's an example.


www.shortcreative.com/proto/pages/bug.html

Has this product been fully tested before launch?

I'm going to run this up to George as I don't have much faith right now.

I've just confirmed, if you add second element to the slide the problem goes away with Firefox. See this page now working correctly.

www.shortcreative.com/proto/pages/bug.html

Hi Howard,

After deep investigation it turned out that this problem is caused by a bug in Firefox 18.

We can not fix it, but it is easily bypassed when you add more than one element on the slide or define a background for the slide.

The Firefox bug exists only in Firefox 18. All previous Firefox version as well all other browsers work just fine.

Unfortunately the Firefox team will be fixing the bug in Firefox 20, so it will take a while. But you can use the bypass in the mean time.

This is the bug:
bugzilla.mozilla.org/show_bug.cgi?id=827577

Greetings,
George

Hello George,
Thanks for the info, that confirms exactly what I had found. I will implement the work-around for now.