Animate Plugin #18
Merged
Animate Plugin #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davist11
approved these changes
Sep 11, 2020
| @@ -0,0 +1,113 @@ | |||
| # animate | |||
There was a problem hiding this comment.
Are there plans to move to a docs folder and just the docs for this? Seems like it would work really well.
There was a problem hiding this comment.
hah #16
absolutely agree
| { | ||
| '[class*="stagger-"] > *': { | ||
| '--stagger-delay': '0s', | ||
| 'transition-delay': `calc(var(--animate-index) * ${staggerInterval.default} + var(--stagger-delay))`, |
|
^ This latest commit is super handy for applying animations on elements that might already specify one of the properties you are trying to transition. Previously, for example, using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Easier version of the README to read here
This was directly inspired by some Viget.com work and a general trend towards our designers wanting to apply these more often.
The README explains the purpose and usage, but one thing I'm especially curious about the verbiage in general that I used. I'll admit that an
animateplugin is not obviously different from theanimationutilities, but it's a rather tricky thing to pin down in a simple name. In short, this generates utilities that would generally be used with Intersection Observer in order to achieve "animate on scroll" or "scroll reveal" type functionalities (those are both existing library names). This plugin isn't intrinsically tied to scrolling, though, so not sure how much that makes sense to mention.In addition, I went with
animate-andstagger-utilities -- let me know how you feel about all these as well!Demo
Made a CodePen with some of the outputted utilities to demonstrate some of these (the
triggerClassis just being toggled in asetIntervalas opposed to being added via Intersection Observer):https://codepen.io/gregkohn/pen/abNVQry?editors=1000