ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #swiper
Goal We want a Swiper instance that loops infinitely but does not automatically transition between slides. Current Constraints Swiper version 8.x or newer. Configuration uses loop: true for infinite looping. Autoplay is disabled by setting autoplay: { delay: 0 } or omitting the autoplay option. Unresolved Behavior When loop: true is combined with a disabled
I'm building a carousel with Swiper (v8) where each slide contains interactive elements—links and a small form—and I need reliable keyboard and screen-reader support. The decision I'm stuck on is whether to enable Swiper's built-in a11y module or disable it and manage focus and announcements myself. The built-in module adds ARIA roles, labels, and arrow-key
Loop mode offsets after the v9 rewrite After migrating a carousel from Swiper 8 to Swiper 11, I am reworking a configuration that uses loop: true , slidesPerView: 'auto' , and centeredSlides: true . Since v9 rearranges the real slide elements instead of cloning them, my old code that relied on duplicated slides and activeIndex no longer maps cleanly to what
Goal Choose a rendering strategy for a Swiper carousel that must display 500+ slides on low-end mobile devices while preserving search visibility and accessibility. Constraints Initial load time and runtime memory are critical on devices with limited RAM. All slide content must be indexable by search engines without JavaScript execution. Assistive technology
The goal is to minimize UI stutter caused by rapid resize events when multiple Swiper instances experience concurrent layout changes, while still ensuring slide dimensions remain accurate for features like virtual slides and lazy loading. In Swiper v8‑v9 the built‑in ResizeObserver does not debounce rapid resize notifications, which can trigger repeated dime
When configuring Swiper for a low‑traffic site, the goal is to reduce bandwidth by deferring image loading until slides become visible. The documented lazy‑loading plugin supports lazy: { loadPrevNext: true } and, when combined with preloadImages: false , should prevent any images from being fetched before they are needed. In many projects, a third‑party ima
Problem Statement When using Swiper.js with the Virtual Slides module in vertical mode, the container height does not adjust after the content of a slide changes post‑initialization. Constraints The instance is configured with virtual: true , direction: 'vertical' , and slidesPerView: 'auto' . The issue appears in Swiper 8.x and 9.x. Questions 1. Does Swiper