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

Could we make *-visible directives work when the element is visible from the start? #29

Closed
Tracked by #81
xstevenyung opened this issue Sep 1, 2021 · 12 comments · Fixed by #171
Closed
Tracked by #81

Comments

@xstevenyung
Copy link

xstevenyung commented Sep 1, 2021

Hello,

As said in the title, In some cases, when doing responsive landing page design (e.g. 15" laptop screen vs 4k screen), it's not really possible to predict 100% of the time when an element will be visible on the first load.

In the cases when a *-visible directive is visible on the first load, the animation never trigger making the element invisible.

I made a repo to illustrate: https://github.com/xstevenyung/v-motion-visible-issue

I could work on a PR if this is something that make sense to change.

Cheers and thanks for your work !

@xstevenyung xstevenyung changed the title Could we make *-visible directives works when the element is visible from the start? Could we make *-visible directives work when the element is visible from the start? Sep 1, 2021
@Tahul
Copy link
Member

Tahul commented Sep 3, 2021

Hey Steven, thank you for your issue!

That seem like great idea!

I would happily review any PR that you submit, please let me know if you need anything concerning the code itself. 😄

@robinvoor
Copy link

robinvoor commented Oct 5, 2021

I have the same issue, some elements are already in the viewport at page load, but not visible initially. Only after scrolling down and back up to those elements will become visible. Is a solution being worked on or does this not have a priority?

@rashidpathiyil
Copy link

Same issue

@JonHerbert
Copy link

Same issue, thanks!

@maddybo
Copy link

maddybo commented May 21, 2022

Same issue :C

@gl-ruslan-honchar
Copy link

Same issue ((

@maddybo
Copy link

maddybo commented May 27, 2022

@Tahul

@Qazzquimby
Copy link

Are people using some kind of workaround?
Given the proposed fix isn't going anywhere, maybe it could be monkeypatched in?

@stonega
Copy link

stonega commented Aug 16, 2022

Same issue

@Tahul Tahul mentioned this issue Sep 11, 2022
13 tasks
@MathiasOxholm
Copy link

This is still an issue :/

@kaypappi
Copy link

This is still a huge issue. And its killing the awesomeness of this package. is there a workaround?

@jordangunther
Copy link

Same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.