Earlier, we mentioned that Tailwind is really bad with theming because you have to style hover, focus, and active states individually.
<div class="hover:bg-blue-500 focus:bg-blue-500 active:bg-blue-500"></div>The good news is Tailwind allows you to create variants with custom variants, so you no longer have to write so many individual variants by yourself. You can combine them into a bigger one.
So if we want to apply the same utility to :hover, :focus and :active, we can combine them into something like a custom-variant. Let’s call it haf (hover, active, focus) variant.
@custom-variant haf { &:hover, &:focus, &:active { @slot; }}Then you can write this instead of repeating the smaller variants:
<div class="haf:bg-blue-500">...</div>If you want to use the variant in CSS, you can use it with @variant.
.selector { @variant haf { /* Your rules here... */ }}That said, I still think pigment is way better for theming because we tend to have to style active states differently from hover and focus states — plus there are other states not mentioned here.
But these custom variants are still very useful for interactions.
The Interact Variant
One of the common things we have to do as developers is to be able to tell whether an element should be active or not.
Most of the time, an element is active when:
- A user interacts with it
- It is in some sort of a selected state.
We have a lot of selectors that allow us to check for these states, like hover, focus, focus-visible, active, [aria-current], [aria-selected="true"], etc. So what I did was to consolidate all of them into a custom variant called interact.
/* Tailwind */@custom-variant interact { &:hover, &:focus-visible, &:active, &[aria-current], &[aria-selected='true'], &[aria-pressed='true'], &[aria-expanded='true'] { @slot; }}I named it interact because I usually activate this when a user interacts with the element, but you can also call it is-active or any other variant you want.
Interact-within Variant
The second variant I find useful is something I call interact-within.
The basic idea here is to select an element when a child element within is being interacted with. It might also have certain states to check for on itself.
Here’s the code for it.
@custom-variant interact-within { &:hover, &:focus-within, &:has( .selected, .checked, [aria-current], [aria-selected='true'], [aria-pressed='true'], [aria-expanded='true'] ) { @slot; }}So far, these are the only two useful custom variants I’ve found.
Welcome! Unfortunately, you don’t have access to this lesson. To get access, please purchase the course or enroll in Magical Dev School.
Unlock this lesson