Duplicated Slides in Infinite Carousel v0.30.0+

[rodrigo-arias]

Description

Encountering an unexpected behavior with react-slick versions 0.30.0 and above. When configuring a carousel with the same number of rows as items and enabling infinite scrolling, slides are duplicated, appearing in both the previous and next items.

Steps to reproduce

1. Install react-slick v0.30.0 or a later version.
2. Set up a carousel with an equal number of rows and items.
3. Enable the infinite scrolling option.
4. Observe the duplication of slides in both the previous and next items.

Feel free to see the difference by rolling back to v.0.29.0 with this CodeSandbox.

The change seems to have originated in #2329 in our case this is a visual breaking change.

[Lala-kumar]

can you specify which file we have to work.

[rjsdnql123]

Could you provide an example? The link isn't working?

[rjsdnql123]

@rodrigo-arias
If the bug I identified is correct, it has been fixed in this pull request. Apologies for the delayed confirmation 😢

Since the maintainer has confirmed, we will soon deploy a new version!

#2366

[bfaulk96]

Using the latest version, this bug still exists

[bfaulk96]

@akiran it looks like the fix was merged into master but never released, is there something stopping it from being released as a new version?

[rodrigo-arias]

@rjsdnql123 Sorry for the late response. I couldn't find a beta, but I tried it by replicating #2366, and I don't see that it solves at least the bug I am reporting (rooted in #2329 and verified by setting the same number of rows and items).

[skrzepij]

Any news about new release?

I've encountered the same issue and as a temporary solution, I've set adaptiveHeight: true.
Somehow this setting hide cloned slides 😬

[rjsdnql123]

@rodrigo-arias @skrzepij

This bug has been fixed. However, since the administrator has not deployed after merging, the bug fix has not been applied.

@akiran Could you please check on this?"

[vsubbotskyy]

It's been 6 months, any updates on this?

[akiran]

This was fixed in the latest version

[rodrigo-arias]

I can confirm that it's finally fixed — thank you @akiran