Carousel slide (fade) flicker at the end of rotation transition
See original GitHub issueOn Safari (macOS/iOS), the fade transition from the last to the first slide causes an flicker for a moment. Prevent this by set z-index
property value one step lower:
.carousel-fade .active.carousel-item-left,
.carousel-fade .active.carousel-item-right {
z-index: 0; /* set to -1 and prevent flicker on Safari */
opacity: 0;
transition: 0s 0.6s opacity;
}
Tested in Safari 11.1.2 and Mobile Safari 12.1.4.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Remove white flash on Slick Slider fade transition
The only way to avoid that would be by stacking each slide on top of each other, then the fade transition would display...
Read more >Carousel - Bootstrap
The carousel is a slideshow for cycling through a series of content, built with CSS 3D transforms and a bit of JavaScript. It...
Read more >Slick carousel animation blinking after the last slide / cloned ...
One way to avoid the bug animation at the end of infinite rotation transition. It will let the slide move into the final...
Read more >Image Carousels and Sliders: Why You Shouldn't Use Them ...
To their credit, once you touch the slider arrows, the automatic rotation stops. Not only that, but when you come back to their...
Read more >Flickity · Options
Enabled by default when carousel has 2 or more slides draggable: '>1' . ... fade. Fades between transitioning slides instead of moving.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via JS Bin and report back with your link, Bootstrap version, and specific browser and OS details.
This is a saved reply.
https://github.com/postcss/autoprefixer/issues/965#issuecomment-355973866
So IMO autoprefixer is fine. Either way, this is an upstream issue if the prefixes change matters at all, and should be reported there.