Virtual Slides and Loop Mode Compatibility Limits

Direct Answers

Indexing consistency: Yes, the virtual slide implementation maintains consistent activeIndex and realIndex values when loop: true is enabled, provided the total number of virtual slides does not change. If you add or remove slides via virtual.update() while the loop is active, the duplicated slide indices can temporarily misalign, causing a jump or blank slide at the boundary.

Documented limits: The combination is stable from Swiper v6.0.0 onward when:

• slidesPerView ≤ number of virtual slides.
• The loop duplicate count (loopedSlides) does not exceed the virtual slide buffer.
• Dynamic updates that change the slide count are performed with the carousel not transitioning (after onTransitionEnd).

Why the Constraints Exist

When loop: true is set, Swiper internally duplicates the first and last slides to create a seamless circular effect. The virtual slide renderer only creates DOM elements for the visible window plus a small buffer. Those duplicated slides are not rendered unless they fall inside the viewport. As long as the dataset size stays constant, Swiper’s internal mapping between virtual indices and real indices remains stable.

Changing the dataset (adding/removing slides) while the loop is active breaks that mapping because the duplicate count must be recalculated. The recommended sequence is:

1. Call swiper.loopDestroy() to remove duplicates.
2. Update the virtual slides array and call swiper.virtual.update().
3. Call swiper.loopCreate() to rebuild duplicates for the new count.

Skipping loopDestroy/loopCreate can leave off‑by‑one errors at the first/last boundary.

Practical Verification Steps

1. Inspect the DOM: only slidesPerView + loopedSlides + buffer elements should have the swiper-slide class.
2. Log swiper.activeIndex and swiper.realIndex before and after a dynamic update; they must stay within 0 .. virtual.slides.length - 1.
3. Run a boundary test: slide to the last slide, trigger a dataset update (add a slide), then advance one more slide. The transition should show the new slide without a jump or duplicate.

Assumptions and Uncertainty

• Assumes Swiper ≥ 6.0.0. Behavior in v5 or earlier may differ.
• Assumes slidesPerView is a fixed number (not "auto") and that the virtual buffer size is the default (usually 1–2 slides).
• If your update logic runs during a transition (e.g., inside onSlideChange), race conditions can still occur even with the destroy/update/create sequence.

One Diagnostic Detail Needed

What Swiper version are you using? If it is below 6.0.0, the loop+virtual combination is not officially supported and the above guidance may not apply.