-
Notifications
You must be signed in to change notification settings - Fork 42
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
Using with <transition-group> #6
Comments
This would be a great feature @longnt80. I originally couldn't get |
@paulcollett - I too got it working using the component tag but that meant that set cols doesn't work. Any chance you got anywhere with resolving this. This is my first Laravel/Vue project so I can't offer much help.
|
@TheFrankman no new update from me as of yet but still thinking this would be a good addition to look into. How did you get on? |
+1 any solution for this? |
+1 I am having lots of issues animating Vuetify cards using this. |
UP !!! |
... What's that supposed to mean? |
Hum.. waiting for solution.. |
Hi all! So I have to wrap each element inside the for-loop with the transition. This means I can't put any styling on the loop-element, and I have to put styling on the inner elements instead. So you'll need an extra wrapper for this.
I used .js animation instead of classes. Then I set an index in my data array and I increase that on the enter hook to delay the animation of each item.
Unfortunately I don't have a demo to show, as I am working locally right now.. but it works fine on my side with both the transitions and the columns. Hope this helps someone! Just an fyi: my particular case was an image gallery, so I also had some functions for rendering the image before animation, but I took it out of the example to stay on topic. So this example would have laggy images. |
+1 Any solution for this yet? |
How do I use this with transition-group? I tried with
masonry
as the component:<transition-group tag="masonry"
but the gutter didn't work, the cols didn't have the gutter as defined.
The text was updated successfully, but these errors were encountered: