animation-name
CSS declaration, and in the case above it’s animation-name: fadeLeft;
, it was just logical to use animation-name: none;
. But since the animation names have to be defined first, any other name that was not declared could have worked in removing the fadeLeft
animation.
I then decided that a bit of animation is actually needed, and a simple fade
will suit my needs.
.animation-fade
to the module itself, my CSS looks like this:
.animation-fade .et_pb_slide_image, .animation-fade .et_pb_slide:first-child .et_pb_slide_image img.active { -webkit-animation-name: fade; -moz-animation-name: fade; -ms-animation-name: fade; -o-animation-name: fade; animation-name: fade; }
Of course, this animation can be changed and tweaked a lot, resulting in advanced and fancy animations, but that’s not the purpose here.
Removing the transition completely would be possible with some fancy JavaScript, but it really doesn’t worth the trouble. Because the fade transition is done by JavaScript gradually changing the opacity, using animation: none;
won’t work. One alternative would be to make the active slide fully opaque from the start, using
.animation-fade .et_pb_slide_image, .animation-fade .et_pb_slide { opacity: 1 !important; }
This makes all slides fully opaque, but the inactive slides also have display: none;
while they’re inactive, so won’t be visible. When they become active, JavaScript replaces it with display: block;
, making the active slide visible. However, that happens slightly before the active slide to become inactive, in order to the fade animation to take place, so for a very short time, 2 layers will be visible. That will be noticeable (and annoying) if the slides images are not the same size, like in the example slides. So keep that in mind when using this method.