-
Notifications
You must be signed in to change notification settings - Fork 89
css transitions
JC Franco edited this page Mar 25, 2025
·
1 revision
We have a few components using idle and active (or similarly named) CSS classes to match a pattern commonly used in transition libs to ensure transitions are run consistently. Maquette has a great breakdown of how this works:
The best way to explain this technique is through an example. Let us say an element with the enterAnimation "slideUp" is added, then the following happens:
- The CSS class "slideUp" is added to the element
- Immediately afterwards, the CSS class "slideUp-active" gets added.
- The browser waits until a CSS transition finishes on the element
- Both CSS classes are removed again.
Worth noting that slideUp represents the idle class in our case.
- Monorepo
- Global Config
- Coding Conventions
- Testing Conventions
- Patching Packages
- Deprecation Guidance
- Continuous Integration
- GitHub Secrets
- Troubleshoot Build Errors
- Tips and Tricks
- NPM FAQ
- Wiki Conventions
- Styling Conventions
- CSS Transitions
- Restricting User Input
- ItemHidden Property
- What Happens When You Scale Vector-Based Icons
- Internationalization
- Introduction
- Getting Started
- Naming Schema
- Semantic Tokens
- Component Tokens
- Web Platform
- Build
- Documentation
- Testing
- Contributing