Replies: 1 comment 15 replies
-
|
@Ra0R Embla doesn't prevent any clicks when the carousel already has been dragged and is in motion. It only prevents clicks when the pointer is pressed and it registers a drag interaction rather than a static click - Which can be configured with the I'm not sure I understand what the problem is. Could you elaborate? Best, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Ra0R, I would very much appreciate if you could test this CodeSandbox and see if you can reproduce the bug there. Best, |
Beta Was this translation helpful? Give feedback.
-
|
@Ra0R I noticed that the sandbox was private. Made it public now. Sorry about that! |
Beta Was this translation helpful? Give feedback.
-
|
@davidjerleke Thank you, it looks like the issue is solved in the sandbox you sent! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for confirming and providing useful information like the screen recording @Ra0R 👍! I will create a bug fix for this. Best, |
Beta Was this translation helpful? Give feedback.
-
|
@Ra0R this bug is now tracked here: Closing this. Thank you 👍! |
Beta Was this translation helpful? Give feedback.
-
Summary
Currently when dragging (with the mouse) with options:
const [emblaRef, emblaApi] = useEmblaCarousel({ loop: false, containScroll: 'trimSnaps', skipSnaps: true });The carousel takes a long time to settle and elements to become clickable again. Is there an option to enable a sampling rate or something similar?
Currently when listening to event scroll:
emblaApi.on('scroll', () => { console.log(emblaApi.scrollProgress()) })The scroll value is updated a lot with of very small values and takes a long time to settle:
Is it possible to define some minimum, e.g. delta = 0.01, such that value changes below that are ignored?
If applicable, which variants of Embla Carousel are relevant to this conversation?
Additional information
No response
CodeSandbox example
No response
Beta Was this translation helpful? Give feedback.
All reactions