You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ONLY the custom properties and a few base styles. **More options, more control, smaller import.**
36
+
Build [custom](#custom)`@keyframe` animations with them and much more. Make multi-part transitions
37
+
that aren't just from and to. You can even break away from the use of attributes and make your own BEM class convention.
38
+
Grab the reigns, grab the hackpack.
37
39
38
40
> Custom properties ship with each `.min.css` as well
39
41
@@ -54,6 +56,8 @@ After `transition.css` has been added to your project, add an attribute to an el
54
56
55
57
> if nothing is happening when using the attributes, it's likely `transition.css` has not loaded
56
58
59
+
Attributes were chosen as the default so there's no question which transition is active. **There can be only 1 at a time.** With classes, for example, what happens when multiple "transition in" classes are applied to an element? Transition.css chooses to default with a state machine approach. See the [custom](#custom) section below for ways to use classes and/or the custom properties, so transition.css can fit into your development environment. It's very flexible, the built in attribute based approach is very easy to hack and customize.
60
+
57
61
Transition.css is very similar to [animate.css](https://animate.style). The docs they've made are excellent and show many examples of advanced usage of libraries like this. You'll notice `transition.css` is very inspired by `animate.css`.
58
62
59
63
<br><br>
@@ -73,16 +77,17 @@ Most of the built in transitions are from the center. Here's how you can set the
0 commit comments