1 (edited by moonunit 2015-07-22 20:27:41)

Topic: Cross Fade causes images to flicker during AutoPlay on Safari

I can't get Cross_Fade to work properly with AutoPlay on Safari. Images flicker during transitions when using Cross_Fade for imageTransitionType and when using AutoPlay. I've tested on the latest versions of Chrome and Firefox (on Windows and Mac) and on IE, and they all work fine. I'm using Safari 6.1.6.

The Galleries are both embedded and full-page, no iframes. You can see the issue more clearly on full-page galleries. I have put up an example page at www.brianwebster.uk/index/juicebox-test. If you resize Safari during a transition, you can briefly see a white frame with the image path in the top left-hand corner.

I updated to JuiceBox 1.4.4, but the issue remains.

Any ideas?

Re: Cross Fade causes images to flicker during AutoPlay on Safari

Do you perhaps have AdBlock installed?
There is a known bug whereby images can flicker when loading in Safari with AdBlock installed when imageTransitionType="CROSS_FADE".
The developers are aware of this bug and hopefully it will be fixed in a future version.
In the meantime, workarounds would be to change the imageTransitionType or uninstall AdBlock (although uninstalling AdBlock would work only for your own computer and not for potential visitors to your site who also use the combination of Safari and AdBlock).

If you are not using AdBlock and this is not the cause of your problem, then please let me know and I will investigate further.
Thank you.

Re: Cross Fade causes images to flicker during AutoPlay on Safari

Gosh! Yes I do have AdBlock. All works fine after disabling it. My client was rather taken with Cross_Fade and I think he will have to reconsider using it until this issue is fixed. Any idea when that might be? Anyway, thank you for the super-speedy response.

Re: Cross Fade causes images to flicker during AutoPlay on Safari

Unfortunately, I do not know when this issue will be fixed. All I can do is assure you that is has been officially logged as a bug and will be addressed in due course. Any estimate I give you with regard to time frame could turn out to be extremely inaccurate. I hope you understand.