Carousel sliding while drag-scrolling vertically on a touch device

[semenets]

Link to original issue: kenwheeler/slick#2521

In the link above you can see description of the bug. I think it's very important to fix that in react-slick too. So can we merge that changes in react-slick? I am ready to do that, if @akiran or somebody else accept this idea.

[vitalim]

I agree with semenets - I think it's important - struggling with it as well on my app

[ghost]

Any update on this issue? I am worried about this issue. Please give a solution for this.

[ghost]

Anybody have solution for this issue on react-slick node_modules?

[vijaybarnwal]

Any update on this?????

[vitalim]

Try this for now:
https://www.npmjs.com/package/react-slick-with-mobile-in-mind
Thanks to semenets

[vijaybarnwal]

Vitalim, What is the changes you have made in given package? Any changes required for settings in slider tag?

[vijaybarnwal]

Hi semenets,

Can you please guide me is any change required for settings in slider tag?

Thanks,
Vijay

[vijaybarnwal]

Vitalim, Is it working for you?

[vitalim]

Yes, I'm using it just like the regular react-slick

[vijaybarnwal]

Have you pass any parameter to slider settings for this issue?

[vitalim]

This is the settings i'm using:
const settings = {
arrows: false,
infinite: false,
}

[vijaybarnwal]

I am getting same issue when scrolling vertically carousal moves/slides horizontally.

Is any fix have you done in https://www.npmjs.com/package/react-slick-with-mobile-in-mind?

Thanks,
Vijay

[naltatis]

The pull request has just been merged in original slick. Can someone port it?

[hustlerism]

Having the same issue as well in my Mobile App.

[ryota-murakami]

I pushed the changes I made to solve this problem in my application to PR.
Please review if it is possible. Thanks!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[emphaticsunshine]

I see the issue is closed but was it resolved?

[ryota-murakami]

@emphaticsunshine I've submitted PR about 2 and half years ago.
According to the comment, this is fixed version 0.22.2 later.

[paulcpk]

Possible duplicate: #1240