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

VisibleOnce Visibility Variant does not work with Nuxt3 SSR / Nuxt Link #134

Closed
CptJJ opened this issue Jun 14, 2023 · 7 comments
Closed
Labels
closed by bot needs reproduction question Further information is requested

Comments

@CptJJ
Copy link

CptJJ commented Jun 14, 2023

When navigating via a nuxt link component div will not appear the second time around. A reload fixes the issue can all styled divs then appear correctly.

@foxilated
Copy link

I came here to submit this exact issue, I've been having much trouble with it.

@cosmincartas
Copy link

I'm having the same issue but not only on visibleOnce variant, on visible as well. As a temporary fix I'm using the useMotion composable which seems to do the job.

const motionVariants: MotionVariants = {
    initial: {
        y: 100,
        opacity: 0
    },
    visibleOnce: {
        y: 0,
        opacity: 1
    }
};
const animatedSectionRef = ref<HTMLElement | null>();
useMotion(animatedSectionRef, motionVariants);

@barbecue
Copy link

@fabienbergerat
Copy link

I'm having the same issue but unfortunately using the composable doesn't seem to fix it.

@BobbieGoede
Copy link
Member

This issue is likely fixed by #171 which is now included in the latest release v2.1.0, but without a reproduction I'm unable to confirm this, can someone check if this issue has been resolved after installing the latest version?

@BobbieGoede BobbieGoede added question Further information is requested needs reproduction labels Feb 23, 2024
Copy link

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

A link to a stackblitz project or public GitHub repository would be perfect. 👌

Please ensure that the reproduction is as minimal as possible.

You might also find these other articles interesting and/or helpful:

Copy link

github-actions bot commented Mar 2, 2024

This issue was closed because it was open for 7 days without a reproduction.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed by bot needs reproduction question Further information is requested
Projects
None yet
Development

No branches or pull requests

6 participants