Swiper: Lazy Load in Multi Row Not working

Created on 3 Feb 2017  路  5Comments  路  Source: nolimits4web/swiper

This is a (multiple allowed):

  • [x] bug
  • [ ] enhancement
  • [ ] feature-discussion (RFC)
  • Swiper Version: 3.4.1
  • Platform/Target and Browser Versions: Windows / Chrome

What you did

new Swiper('.swiper-container-game', { slidesPerView: 6, slidesPerColumn: 3, slidesPerColumnFill: 'row', slidesPerGroup:6, nextButton: '.paginator-next', prevButton: '.paginator-prev', pagination: '.location-box span', paginationType: 'custom', preloadImages: false, lazyLoading: true, observer: true, lazyLoadingInPrevNext: true, paginationCustomRender: function (swiper, current) { return current; } });

Expected Behavior

All 18 slides in first view Port ( 6 Slider Per Row * 3 Slider per Column ) should be lazy loaded

Actual Behavior

only the first 6 was lazy loaded and also in next slide only 6 first are lazy loaded . all the rest always stuck on preloader .

P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.

Before you open an issue, please check if a similar issue already exists or has been closed before.

Most helpful comment

I have just tried this using 4.0.7 & still the issue is still there.

All 5 comments

Sent a pull request which solve this issue.
Pull #2008

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.

If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

  • Clearly describe the issue including steps to reproduce when it is a bug.
  • Make sure you fill in the earliest version that you know has the issue.
  • Provide live link or JSFiddle/Codepen or website with issue

Hello nolimits4web.

Second column does not lazyload.
Version: https://cdnjs.cloudflare.com/ajax/libs/Swiper/4.0.6/js/swiper.js

I provided codepen with the problem: https://codepen.io/larsmqller/pen/WXEBdG

How can we fix? :)

I have just tried this using 4.0.7 & still the issue is still there.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings