Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Swiper carouse version up to 4? #4170
Thank you for the great plugin and love your work.
I have found you are using swiper 3.4.2. But there is already Swiper 4.2.2.
one more question, is there any reason to use 2 slider js? you are using "slick slider" and "swiper" as well.
Thank you again,
Also please update the swiper library to the latest version as soon as possible.
allonsacks: I know, it sucks, doesn't it? This is typical behavior in web development, even beyond Elementor. You'll find the same situation exists with WordPress other plugins. For example, you install WooCommerce, and now its JS/CSS files are loaded on every page of your site. Inspect any other CMS or complex system, and chances are good you'll find the same situation too.
Developers build a tool, but they have no way of knowing where the user will actually use it. So it's much safer, convenient/lazy and cost-effective just to load all resources on every page. The idea is, if it becomes a problem for certain power users, let them figure it out. Anyways, in theory, after the first loading, the files get cached by the client browser, so from this perspective, it's not terrible (this is the discussion-closing counter-argument typically given by developers).
What is the flipside?
The developer would have to make an interface to allow the user fine-grained management of resource loading across pages and posts. Extra work. And to top it off, now you're just made support that much more of a nightmare.
Take a look at this plugin, it helps you do selective-loading of WP plugins. It works. But look at its interface. It's not nice or intuitive. It could be better designed. The point is it is an interface that needs to exist and adds complexity.