Both Swiper and Flickity demos are working perfectly fine, even on iPhone 13 Pro AND chrome browser.
Splide demos on iPhone 13 Pro:
About 80 % of all demos seem to have a transition/transform issue on only chrome browser (itās not only autoplay, other effects too). 20 % of the demos are working perfectly fine.
Concerning bug report:
Will add my experiences there too. Canāt add a video now cause I am only on the phone these days and handling uploads/links/ā¦ always is a bit inconvenient from the phone as we all know. Will add some end of this week!
Regarding ACSS:
I also think that this is not the issue, cause itās happening on splide demo site too (and I donāt think that they are using acss )
Thanks for your statement too. Will keep this in mind, but it seems that itās caused by a big in Splide library (at least at this point of time).
Concerning ACSS:
I didnāt check or test it myself yet, but if ACSS really gives us no option at all, I fully support the idea, that we should have an option to turn on/off reduced motion and decide freely on our own.
Ok, so thereās a hidden (not documented) option in Splide, - useScroll.
If this is set to true, itāll avoid using CSS transitions for the sliding animation, which is where the issue with Chrome on this device must be. (for the devs - you can see the condition at line 2914 in splide code - splide/splide.js at master Ā· Splidejs/splide Ā· GitHub)
As Bricksā slider has the ability to add in custom options for the slider, instead of using the built-in UI settings, this would allow you to add this option in manually alongside other options.
The ideal future solution would be some condition built in, so most browsers make use of the CSS transitions but the one(s) where this doesnāt work correctly, instead use this āuseScrollā option so the issue goes inseen.
Hey Michael,
I read along diligently Does the scroll option work for you? Have you tested it?
@wplit Thanks so much for investigating extensively! As far as I can see, itās more splideās responsibility (or chrome) to fix the problem permanently, isnāt it?
Surely we could make the āscrollā option available as a toggle, but that wonāt solve the problem in the long run
Sorry @timmse, I must have overlooked your question.
Yes, @wplitās demo solution with UseScroll did work for me on iPhone 13 Pro (same as @HeroRox also stated).
This is what David Browne recommended (and as a non-dev this sounds legitimate to me): The ideal future solution would be some condition built in, so most browsers make use of the CSS transitions but the one(s) where this doesnāt work correctly, instead use this āuseScrollā option so the issue goes inseen.
Stefan and David, good news. This issue is solved (at least on my end) by updating my iPhone 13 Pro to iOS 16.2. Turned out that it has been an iOS issue.
Hello, sorry if I may have missed something in the threadā¦ But for me the problem is not solved. My animations (with the nestible slider, but also via conditions (event: enter viewport) are completely disabled when I have āreduce motionā enabled. This is true for all my ios devices, MacBook Pro and my Windows 10 desktop. Namely in Firefox, Chrome and Safari (all latest versions).
I understand the point of the āreduce motionā option, of course. However, I donāt use wild motionā¦ but āonlyā a very smooth fade transition in the heroslider of my homepage.
Is there a way in Bricks to persuade the slider to autoplay, even with the āreduce motionā option enabled?
)
Does the scroll option work for you? Have you tested it?
