Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to Disable Rubber Band Effect when Loop is set to False #517

Closed
1 task done
jakedowns opened this issue Jul 6, 2023 · 3 comments
Closed
1 task done

Option to Disable Rubber Band Effect when Loop is set to False #517

jakedowns opened this issue Jul 6, 2023 · 3 comments
Labels
duplicate This issue or pull request already exists

Comments

@jakedowns
Copy link

jakedowns commented Jul 6, 2023

Feature request is related to

  • embla-carousel (core package) 6.2.0

Is your feature request related to an issue?

#42

Describe the solution you'd like

i'd like an option or workaround to disable rubber-banding on the first / last item when loop is False
i use embla nested within ANOTHER swiper element, and when the user swipes right on the first image,
i'd like the outer container to pick up the pan gesture, and animate the outer container

currently: i see the inner slideshow moving AND the outer container moving simultaneously, which just isn't what my client desires.

Describe alternatives you've considered

  1. disabling 1:1 swipe-based page naviation effect in favor of an Arrow overlay element coming into view

    still has issue of nested gesture recognition (bad visual affordance to user that there's more media to view, rather than that they've reached a hard Stop edge and will begin controlling the OUTER container)

  2. disable visual feedback and just respond to swipe (bad ux)

  3. disable swipe gesture stick to alternative arrow button navigation (would love to keep swiper like "native app" feeling)

Additional context

you can see the nested swiper effect / issue if you visit this page on mobile:
https://www.wright20.com/auctions/2023/07/2021-art/100

@jakedowns jakedowns added the feature request New feature or request label Jul 6, 2023
@davidjerleke
Copy link
Owner

Hi @jakedowns,

Did you try this solution? I also think you missed this information.

Best,
David

@jakedowns
Copy link
Author

oh derp, i had copied a version that still used dangerouslyGetEngine

i see internalEngine() was the updated way to reference it

works great!

thanks for such a great plugin, and i appreciate your attention to detail!

@davidjerleke
Copy link
Owner

@davidjerleke davidjerleke added duplicate This issue or pull request already exists and removed feature request New feature or request labels Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants