Ensuring that drag does not move slides more than options.flickMaxPages allows

[Kreeg]

Description

If you drag the slider too fast, it moves more than options.flickMaxPages.
For example, there is a problem with caused with this config.

{
  flickMaxPages: 1,
  perMove: 1,
  perPage: 1,
}

video5411494184043422802.mp4

In this video you can see that sometimes slider moves more than 1 page. After some digging I found that this is computeDestinations problem. In fact, it's getPosition that causes this error. If you drag fast, it calculates that you are already at the next slide, but in reality, you are not.
So in this case I just added a new additional check that splide does not move more than it should.

Sorry for no related issue. This started as a local critical bug on our website so we can't wait too long. We have already switched to a forked version and have tested it in production mode. But I added more unit-tests to be sure.

[simonbrunel]

Sorry for no related issue.

@Kreeg actually, there is at least one: #1002

[tomikaka22]

Would love this to be fixed.

[Kreeg]

You can switch to our fork for now npm i git@github.com:IT-GRI/splide.git