-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Component Jitters at Screen Edges When Using v-motion
Slide Presets Along Y-Axis
#215
Comments
Technically speaking this is working as intended but I understand the confusion. The slide visible bottom preset moves the element up when it enters the viewport and does the reverse when it leaves the viewport, but by moving back down the element once again enters the viewport, triggering an infinite loop at this scroll offset (in an out of viewport). The easiest workaround is using |
Thank you for the detailed explanation and for clarifying how the Should I proceed to close this issue as resolved from my end?
|
Ah if this resolves your issue we can close it! 😄 Let me know if you have any more questions, I'll add a notice (at some point) in the docs to explain this behavior to hopefully prevent others from running into the same issue. |
System info
Nuxt.js: (3.8.2)
Reproduction
Code Snippet:
Steps to Reproduce:
v-motion
slide preset that slides along the y-axis.Describe the bug
Hello,
I encountered an issue while using
v-motion
slide presets that involve sliding along the y-axis. The problem arises at the edges of the screen, where the component begins to jitter up and down. This behavior disrupts the smoothness of the animation.Expected Behavior:
The component should slide smoothly without any jittering or unwanted up and down movement at the screen edges.
Actual Behavior:
The component jitters up and down when it reaches the edges of the screen, causing a disruption in the smoothness of the animation.
Additional Information:
I have recorded a video to demonstrate the issue.
Additional context
Logs
No response
The text was updated successfully, but these errors were encountered: