Plugin Support
Milos
(@miloss84)
Hi there,
Thanks for following up, and I’m sorry to hear how frustrating this has been.
To help us investigate this properly, could you please share a bit more information about the mobile devices where the issue occurs?
Specifically, it would be helpful to know:
- The exact phone models where the Ken Burns effect and slideshow are not working
- The OS version running on those devices (Android / iOS version)
- Whether the issue happens in the device’s default browser or across multiple browsers
Knowing how old the devices are and which browsers they use will help us determine whether this is related to browser/device compatibility or something that should still be supported.
Also, please note that Elementor supports devices and environments that meet our system requirements. You can review them here:
https://elementor.com/help/requirements/
Once we have the device details, we’ll be able to test this more accurately and continue investigating the issue.
Best regards,
cBaz
(@sebascalidoso)
@miloss84 Help me understand something, why downgrading the Elementor version enable the Ken Burns effect again? Seems like the Ken Burns effect are not a big deal regarding what was mentioned here that needs high performance enabled or whatever, simply css code should trigger the effect with no problems as seen here https://codepen.io/befa1/pen/GRKMNPm
cc: @gemart1
Hi @miloss84 ,
I’ll give you the details, but honestly, we’ve been over this four months ago and it’s frustrating to start from scratch.
I’m using a Huawei P40 Lite running Android 10 (EMUI 10.1). My browsers (Chrome and Firefox) are fully updated to their latest available versions. The issue is identical on other mid-range devices from that generation as well.
Here’s the thing: on version 3.32.5, everything works perfectly. The Ken Burns effect is smooth and the slideshow never skips a beat. The moment I update to 3.33.0 or anything newer, the slideshow just freezes on the second image and the animation dies.
As @sebascalidoso pointed out, this isn’t some high-performance NASA technology – it’s just CSS and JS. If my phone can run the effect on 3.32.5, the hardware is obviously NOT the problem. The problem is that something in your new code (maybe the new Variables Manager or the way you updated Swiper.js) is crashing on older WebKit engines.
Please don’t just send me the “System Requirements” link again. My phone is more than capable of sliding two pictures with a zoom effect – it’s been doing it on Elementor for years until this specific update.
Could you please have someone actually compare the slideshow JS logic between 3.32.5 and 3.33.0? There is a clear regression there that’s breaking the experience for everyone who doesn’t buy a new iPhone every year.
I really want to update my site for security reasons, but I can’t leave my homepage looking broken.
Best regards,
Todor
cBaz
(@sebascalidoso)
I also noticed that this update damages not just the Ken Burns effect but also an effect called “Overlay Direction Aware” also pure CSS, downgrading to 3.32.5 does not cause any issues at all, on a site without elementor everything up to date and tested in 2 different builders up to date works great, elementor on it’s latest version not working at all. Very sad seeing this from my favorite builder.
@miloss84 @gemart1
Plugin Support
Milos
(@miloss84)
Hi there,
We’re sorry for any inconvenience this may cause, but please note that we cannot guarantee compatibility with older operating systems or browsers. As technology continues to evolve, support for outdated platforms is gradually phased out, as they no longer meet modern performance and security standards.
Additionally, Android 10 officially stopped receiving regular security updates from Google in March 2023. This means that newly discovered vulnerabilities are no longer being patched, which can put your device and data at risk.
Because of this, using Android 10 today is not only a compatibility concern but also a security risk. For the best and safest experience, we strongly recommend updating your device to a newer version of Android, if possible.
Thank you for your understanding.
cBaz
(@sebascalidoso)
@miloss84 will all your respect you are not understanding the issue here, no matter how old the device is, for example if I use my desktop pc i9 10900K 5.0Ghz and has 128GB of ram with a 3090ti the issue persist on all browsers tested, Brave, Chrome, Firefox, Opera, Edge (All Tested in Desktop environment with the best performance possible)
Hi @miloss84 ,
Suggesting that a user should buy a new phone because an Elementor widget fails is not a solution – it’s a lazy excuse. As @sebascalidoso clearly stated, this bug persists on high-end desktop environments too, so your “outdated Android 10” argument is completely irrelevant.
The truth is, your JS logic after v3.32.5 is broken. To prove how poorly optimized your current slideshow engine is, I’ve completely removed the Elementor Slides widget and replaced it with a simple custom CSS/JS solution using the exact same images.
The result? My “insecure” and “outdated” device now runs the Ken Burns effect perfectly and smoothly, while my Mobile PageSpeed score jumped to 90.
It’s embarrassing that a multi-million dollar builder fails where a few lines of manual code succeed flawlessly. Instead of sending me links to “System Requirements”, maybe you should send this to your dev team so they can fix the regression they’ve ignored for months. I’m moving forward with my custom fix since Elementor is clearly no longer reliable for professional use.
Best regards,
Todor
cBaz
(@sebascalidoso)
@gemart1 Sound to me that they are using AI in their code and not looking on what they push 🙂
Plugin Support
Milos
(@miloss84)
Hi there,
Thank you for your detailed feedback.
We sincerely apologize for the frustration this situation has caused and for any impression that your concerns were not properly acknowledged. Suggesting a device upgrade is not an appropriate solution if the same issue occurs on high-end desktop environments, and we understand why this would be frustrating.
We also appreciate the effort you put into testing an alternative solution and comparing performance using the same images and effect. This kind of insight is extremely valuable, as it helps us better understand the behavior and identify potential issues.
Since this appears to require a deeper technical investigation, the best next step would be to have our development team review the behavior in detail. If you would like assistance with these kinds of issues, we advise you to visit our GitHub page at http://www.github.com/elementor and open an issue with as much technical information as possible steps to reproduce, environment details, and ideally a comparison between version 3.32.5 and the current version. This will allow our developers to properly analyze and address the potential regression.
Once again, we apologize for the inconvenience, and we truly appreciate you taking the time to share such constructive and actionable feedback.
Plugin Support
Rica
(@ricav)
Due to inactivity, this ticket has been closed.
