You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If swiper is initiated above the fold, the first slide should get loading="eager" and the rest loading="lazy". Update "10.2.0" changed Element lazy preloader lookup logic and now all slides have to use lazy="true" in order to work. Can be verified with npm run element adding some images.
Even if all slides have lazy="true" and images loading="lazy", the swiper is initialised correctly but preloader always stays visible and never disappears.
Expected Behavior
We should still be able to load the first slide without lazy in eager fashion for the above the fold content. The preloader has to disappear once the image is loaded.
Hello @nikitasol. Please provide a online reproduction by codesandbox or a minimal GitHub repository. You can fork one of our demos in codesandbox to get start. Issues labeled by missing demo will be closed if no activities in 3 days.
Check that this is really a bug
Reproduction link
https://codesandbox.io/p/sandbox/swiper-default-forked-75kk6t?file=%2Findex.html%3A52%2C37
Bug description
Two connected issues:
npm run element
adding some images.Expected Behavior
We should still be able to load the first slide without lazy in eager fashion for the above the fold content. The preloader has to disappear once the image is loaded.
Actual Behavior
No response
Swiper version
10.2.0
Platform/Target and Browser Versions
macOS Safari 16.4 and macOS Chrome 115
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: