Arbitrary variants for custom selectors in Tailwind - Browser Rendering Trace

Render Flow - Arbitrary variants for custom selectors

[Parse Tailwind config] -> [Identify arbitrary variant syntax] -> [Generate CSS selector with custom variant] -> [Apply styles to matched elements] -> [Render updated styles in browser]

Tailwind reads the custom variant syntax inside square brackets, converts it into a CSS selector, then applies the styles to elements matching that selector, updating the page visually.

Render Steps - 3 Steps

Code Added:<button class="p-4">Click me <svg></svg></button>

Before

[ ] (empty page)

→

After

[button]
|_ 'Click me '
|_ [svg]

The button with padding appears with text and an SVG inside, but no background color yet.

🔧 Browser Action:Creates DOM nodes and applies default styles

Code Sample

A button with padding that changes background color to light green only if it contains an SVG element.

Tailwind

<button class="[&:has(svg)]:bg-green-200 p-4">Click me <svg></svg></button>

Tailwind

[&:has(svg)]:bg-green-200 { background-color: #bbf7d0; }

Render Quiz - 3 Questions

After applying step 2, what visual change do you see on the button?

A Button padding increases

B Button text color changes to green

C Button background changes to light green because it contains an SVG

D No visual change

Common Confusions - 2 Topics

Why doesn't the background color apply if the button has no SVG?

The custom variant uses :has(svg) which only matches buttons containing an SVG child. Buttons without SVG do not match, so no background color is applied.

💡 Custom variants with :has() only style elements that contain the specified child.

Can I use arbitrary variants with any CSS selector?

Yes, but the selector must be valid CSS and supported by browsers. Tailwind wraps it in square brackets to generate the correct CSS selector.

💡 Use square brackets to write any valid CSS selector as a variant.

Property Reference

Property	Value Applied	Selector Type	Visual Effect	Common Use
Arbitrary variant	[&:has(svg)]	Custom CSS pseudo-class	Applies styles only if element has SVG child	Conditional styling based on child elements
Background color	bg-green-200	CSS background-color	Changes background to light green	Highlight elements meeting condition
Padding	p-4	CSS padding	Adds space inside element	Spacing for clickable areas

Concept Snapshot

Arbitrary variants in Tailwind use square brackets to write custom CSS selectors. Example: [&:has(svg)]:bg-green-200 applies styles only if element contains an SVG. This allows conditional styling based on child elements. Use valid CSS selectors inside brackets. Common for advanced UI states and interactions.

Practice

1. What does an arbitrary variant in Tailwind CSS allow you to do?

easy

A. Use custom CSS selectors inside Tailwind classes

B. Write JavaScript code inside Tailwind classes

C. Change Tailwind's default color palette

D. Disable Tailwind's responsive features

Solution

1. Step 1: Understand Tailwind's arbitrary variants

   Arbitrary variants let you write custom CSS selectors inside Tailwind by wrapping them in square brackets.

2. Step 2: Compare options

   Only Use custom CSS selectors inside Tailwind classes correctly describes this feature; others describe unrelated Tailwind features.

3. Final Answer:

   Use custom CSS selectors inside Tailwind classes -> Option A

4. Quick Check:

   Arbitrary variants = custom selectors [OK]

Hint: Look for custom selector usage in square brackets [OK]

Common Mistakes:

• Thinking arbitrary variants change colors
• Confusing with JavaScript or responsive features
• Assuming it disables Tailwind features

2. Which of the following is the correct syntax to apply a hover style using an arbitrary variant in Tailwind?

easy

A. hover:[&:hover]:text-blue-500

B. [&:hover]:text-blue-500

C. hover:text-blue-500

D. [hover]:text-blue-500

Solution

1. Step 1: Understand arbitrary variant syntax

   Arbitrary variants use square brackets with a selector inside, e.g., [&:hover].

2. Step 2: Identify correct usage for hover

   [&:hover]:text-blue-500 uses the correct syntax: [selector]:utility, here [&:hover]:text-blue-500.

3. Final Answer:

   [&:hover]:text-blue-500 -> Option B

4. Quick Check:

   Arbitrary variant syntax = [&:hover]:utility [OK]

Hint: Look for square brackets with & and pseudo-class inside [OK]

Common Mistakes:

• Adding 'hover:' before arbitrary variant
• Using brackets without &
• Misplacing brackets around 'hover'

3. What will be the effect of this Tailwind class on a button element?

<button class="[&:focus-visible]:ring-2 [&:focus-visible]:ring-blue-600">Click me</button>

medium

A. The button never shows a ring

B. The button always has a blue ring

C. The button gets a blue ring when it is focused and visible

D. The button gets a blue ring only on hover

Solution

1. Step 1: Analyze the arbitrary variant selectors

   The class uses [&:focus-visible] which applies styles only when the button is focused and visible.

2. Step 2: Understand the applied styles

   ring-2 and ring-blue-600 add a blue outline ring of thickness 2 on focus-visible state.

3. Final Answer:

   The button gets a blue ring when it is focused and visible -> Option C

4. Quick Check:

   Arbitrary variant with :focus-visible = ring on focus [OK]

Hint: Focus-visible means ring appears only on keyboard focus [OK]

Common Mistakes:

• Thinking ring is always visible
• Confusing focus-visible with hover
• Ignoring the arbitrary variant selector

4. Identify the error in this Tailwind class usage:

<div class="[&hover]:bg-red-500">Alert</div>

medium

A. Incorrect pseudo-class syntax, should be [&:hover]

B. Square brackets should not be used here

C. Missing ampersand (&) before hover

D. bg-red-500 is not a valid Tailwind color

Solution

1. Step 1: Check the arbitrary variant syntax

   The pseudo-class hover must be preceded by a colon and ampersand inside brackets: [&:hover].

2. Step 2: Identify the mistake

   The class uses [&hover] missing the colon, so it is invalid syntax.

3. Final Answer:

   Incorrect pseudo-class syntax, should be [&:hover] -> Option A

4. Quick Check:

   Pseudo-class needs colon after & [OK]

Hint: Pseudo-classes need &: e.g., [&:hover] not [&hover] [OK]

Common Mistakes:

• Omitting colon before pseudo-class
• Using brackets incorrectly
• Assuming bg-red-500 is invalid

5. You want to style a child span inside a div only when the div is hovered, using Tailwind arbitrary variants. Which class should you add to the div?

hard

A. [&>span:hover]:text-green-600

B. [&>span]:hover:text-green-600

C. hover:[&>span]:text-green-600

D. [&:hover>span]:text-green-600

Solution

1. Step 1: Understand the selector goal

   You want to style the span child only when the div is hovered, so the hover is on the parent.

2. Step 2: Choose correct arbitrary variant syntax

   The selector [&:hover>span] means when the div is hovered, style its direct child span.

3. Step 3: Check other options

   [&>span:hover]:text-green-600 styles span on its own hover, not div's hover. hover:[&>span]:text-green-600 and D have incorrect syntax or order.

4. Final Answer:

   [&:hover>span]:text-green-600 -> Option D

5. Quick Check:

   Parent hover affecting child = [&:hover>span] [OK]

Hint: Parent hover affecting child uses [&:hover>child] [OK]

Common Mistakes:

• Applying hover on child instead of parent
• Misplacing brackets or colons
• Using hover: outside arbitrary variant incorrectly