Incorrect Behavior of autoScrollOffset Parameter in Swiper When Switching Thumbnails

[SerhiiStepanenko]

Check that this is really a bug

• I confirm

Reproduction link

https://codesandbox.io/p/sandbox/incorrect-behavior-of-autoscrolloffset-parameter-in-swiper-when-switching-thumbnails-vqx7qg?file=%2Fsrc%2FModalSlider.js%3A165%2C33

Bug description

In Swiper, the autoScrollOffset parameter is used to automatically scroll thumbnails by a specified number of slides from the edge upon their activation. According to the documentation, setting it to a value, for example, 1, should result in automatic scrolling of thumbnails when the last visible thumbnail (1 position from the edge) gets activated. However, the switching of thumbnails does not adhere to the defined autoScrollOffset value, leading to incorrect positioning of thumbnails post-activation.

Uploading WFTU3831.MP4…

Expected Behavior

It is expected that setting the autoScrollOffset parameter with a certain value will prompt Swiper to automatically scroll the thumbnails by the specified number of positions from the edge upon their activation. This should ensure smooth and intuitive navigation through the thumbnails, allowing users to always view the active thumbnail in the context of its surrounding slides, thus enhancing visual interaction and navigation.

Actual Behavior

In practice, when setting the autoScrollOffset with any value, Swiper fails to execute the expected automatic scrolling of thumbnails upon activation. Instead, thumbnails switch incorrectly, not maintaining the specified offset from the edge, which leads to confusion and deteriorates the user experience when interacting with the slider. This issue is observed across various Swiper configurations and on a wide range of devices.

Swiper version

11.1.1

Platform/Target and Browser Versions

iOS, Safari

Validations

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
• Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

• I'm willing to open a PR

[SerhiiStepanenko]

WFTU3831.MP4