centeredSlides: 'true' and .swiper-slide { width: auto; } make the slider start at the last image with missing images to the right

[Stanzi1791]

Hi,

When I'm using centeredSlides: 'true' in combination with .swiper-slide { width: auto; }
the slider starts with the last image centered, images to the right of the centered image are missing.

After the first autoplay "move", the first image is centered and the images to the right are loaded,
this is the state I would have expected Swiper to start in.

Fiddle here (the first image is the green one):
https://jsfiddle.net/wq7j8Lep/2/ (you may have to refresh the page to see the behaviour above)

The fiddle uses Swiper 7.0.8, but I've also seen this behaviour in Swiper version 5.3.6.

If I turn off autoplay and look at the html, it looks like the "swiper-slide-active" class is getting assigned to the wrong slide (the last one) when the page first loads. Did I use the plugin wrong or is there a workaround for this?

Kind regards,
Marleen

[Stanzi1791]

I went through the Swiper code and noticed the for loop inside the if (params.normalizeSlideIndex) { } in the slideTo function is in this case incorrectly recalculating the slideIndex, causing the "swiper-slide-active" class to be added to the wrong slide.

Adding normalizeSlideIndex: false to the parameters of the Swiper appears to fix the problem.
It's not clear from the documentation what this parameter is supposed to do, so this might have other side effects I haven't noticed yet.

Hopefully this will be of use to others.

Fiddle with the fix: https://jsfiddle.net/wxo9ugkz/

[myrecs]

also faced with problem that active index calculated wrong in case when using Auto slides per view and slideToClickedSlide:true. It behaves like so: if left slide if hidden less than half of its width (in code it calculates width / 2), then swiper doesnt slide to it, because it still sets activeIndex to that left slide, but it should slide, cause only part of slide is visible! Disabling normalizeSlideIndex solves this issue, but i think it's a bug and you should add some cases in code for such situations.