Disabled state styling in Tailwind - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to disable the button using Tailwind CSS.

Tailwind

<button class="bg-blue-500 text-white py-2 px-4 rounded [1]" disabled>Click me</button>

Drag options to blanks, or click blank then click option'

Aopacity-50 cursor-not-allowed

Bhover:bg-blue-700

Ctext-gray-700

Dborder-2 border-red-500

Attempts:

3 left

💡 Hint

Common Mistakes

Using hover styles on a disabled button.

Not changing the cursor to indicate disabled state.

Using opacity-50 makes the button look faded, and cursor-not-allowed changes the cursor to show it's disabled.

2fill in blank

medium

Complete the code to apply a gray background when the button is disabled.

Tailwind

<button class="py-2 px-4 rounded bg-blue-600 text-white disabled:[1]" disabled>Submit</button>

Drag options to blanks, or click blank then click option'

Abg-green-500

Bbg-red-500

Cbg-gray-400

Dbg-yellow-300

Attempts:

3 left

💡 Hint

Common Mistakes

Using a bright color for disabled state.

Not using the disabled: prefix.

The disabled:bg-gray-400 class applies a gray background only when the button is disabled.

3fill in blank

hard

Fix the error in the code to correctly style the disabled input field.

Tailwind

<input type="text" class="border p-2 rounded [1]" disabled />

Drag options to blanks, or click blank then click option'

Adisable:border-gray-300 disable:bg-gray-100

Bdisable:border-red-500 disable:bg-red-100

Cdisabled:border-gray-700 disabled:bg-white

Ddisabled:border-gray-300 disabled:bg-gray-100

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disable:' instead of 'disabled:'.

Applying styles without the disabled prefix.

The correct Tailwind prefix for disabled state is disabled:. It applies styles only when the element is disabled.

4fill in blank

hard

Fill both blanks to style a disabled button with faded text and no pointer events.

Tailwind

<button class="bg-green-500 text-white py-2 px-4 rounded disabled:[1] disabled:[2]" disabled>Save</button>

Drag options to blanks, or click blank then click option'

Aopacity-40

Bcursor-not-allowed

Cpointer-events-none

Dunderline

Attempts:

3 left

💡 Hint

Common Mistakes

Using cursor styles instead of pointer-events.

Not applying both styles for full disabled effect.

opacity-40 makes the button look faded, and pointer-events-none disables mouse interactions when disabled.

5fill in blank

hard

Fill all three blanks to style a disabled input with gray border, light background, and no text selection.

Tailwind

<input type="text" class="border-2 rounded p-2 disabled:[1] disabled:[2] disabled:[3]" disabled />

Drag options to blanks, or click blank then click option'

Aborder-gray-400

Bbg-gray-200

Cselect-none

Dtext-red-500

Attempts:

3 left

💡 Hint

Common Mistakes

Using bright colors for disabled input.

Forgetting to disable text selection.

When disabled, the input has a gray border (border-gray-400), a light gray background (bg-gray-200), and text selection is disabled (select-none).

Practice

1. What does the disabled: prefix in Tailwind CSS do?

easy

A. Removes the element from the page

B. Disables the element functionality

C. Applies styles only when the element has the disabled attribute

D. Makes the element visible only on hover

Solution

1. Step 1: Understand the disabled attribute

   The HTML disabled attribute marks an element as inactive or unusable.

2. Step 2: Role of Tailwind's disabled: prefix

   The disabled: prefix applies CSS styles only when the element is disabled, allowing visual changes without affecting functionality.

3. Final Answer:

   Applies styles only when the element has the disabled attribute -> Option C

4. Quick Check:

   disabled: prefix = style on disabled [OK]

Hint: Remember disabled: styles only affect disabled elements [OK]

Common Mistakes:

• Thinking disabled: disables functionality
• Confusing disabled: with hover: or focus:
• Assuming disabled: removes elements

2. Which Tailwind CSS class correctly changes the cursor to 'not-allowed' when a button is disabled?

easy

A. disabled:cursor-not-allowed

B. cursor-not-allowed

C. cursor-disabled

D. disabled:cursor-disabled

Solution

1. Step 1: Identify the cursor style for disabled state

   The cursor style for disabled elements is not-allowed, which shows a 'no' symbol.

2. Step 2: Use Tailwind's disabled prefix

   To apply this style only when disabled, use disabled:cursor-not-allowed. Plain cursor-not-allowed applies always.

3. Final Answer:

   disabled:cursor-not-allowed -> Option A

4. Quick Check:

   disabled:cursor-not-allowed = correct syntax [OK]

Hint: Use disabled: prefix before cursor class for disabled styling [OK]

Common Mistakes:

• Using cursor-not-allowed without disabled:
• Using non-existent cursor-disabled class
• Placing disabled: after the class name

3. What will be the background color of this button when disabled?

<button disabled class="bg-blue-500 disabled:bg-gray-400">Click me</button>

medium

A. Red (#ef4444)

B. Blue (#3b82f6)

C. No background color

D. Gray (#9ca3af)

Solution

1. Step 1: Check the button's disabled attribute

   The button has the disabled attribute, so disabled styles apply.

2. Step 2: Analyze Tailwind classes for background

   The normal background is bg-blue-500. When disabled, disabled:bg-gray-400 overrides it to gray.

3. Final Answer:

   Gray (#9ca3af) -> Option D

4. Quick Check:

   disabled attribute triggers disabled:bg-gray-400 [OK]

Hint: Disabled attribute triggers disabled: styles override base [OK]

Common Mistakes:

• Ignoring disabled: prefix effect
• Assuming base bg-blue-500 stays
• Confusing gray-400 with gray-500

4. Identify the error in this Tailwind usage for disabled styling:

<input disabled class="disabled:bg-gray-300 cursor-not-allowed" />

medium

A. Cursor style should use disabled: prefix

B. Cannot style input elements with Tailwind

C. disabled:bg-gray-300 is invalid syntax

D. Missing disabled attribute on input

Solution

1. Step 1: Check the disabled attribute presence

   The input has the disabled attribute, so disabled styles can apply.

2. Step 2: Analyze cursor style usage

   The cursor style cursor-not-allowed applies always. To apply only when disabled, it should be disabled:cursor-not-allowed.

3. Final Answer:

   Cursor style should use disabled: prefix -> Option A

4. Quick Check:

   Cursor needs disabled: prefix for disabled state [OK]

Hint: Add disabled: prefix to cursor styles for disabled elements [OK]

Common Mistakes:

• Forgetting disabled: prefix on cursor
• Thinking disabled:bg-gray-300 is wrong
• Assuming inputs can't be styled

5. You want a button to have a blue background normally, but when disabled, it should have a gray background and the text should be lighter gray. Which Tailwind classes achieve this?

hard

A. bg-blue-600 disabled:bg-gray-400 text-white text-gray-300

B. bg-blue-600 disabled:bg-gray-400 disabled:text-gray-300 text-white

C. bg-blue-600 bg-gray-400 disabled:text-gray-300 text-white

D. bg-blue-600 disabled:bg-gray-400 text-gray-300 disabled:text-white

Solution

1. Step 1: Set normal background and text colors

   Use bg-blue-600 for blue background and text-white for white text normally.

2. Step 2: Apply disabled styles with prefix

   Use disabled:bg-gray-400 for gray background and disabled:text-gray-300 for lighter gray text when disabled.

3. Step 3: Verify order and prefixes

   Classes must have disabled: prefix for disabled styles; base styles apply otherwise.

4. Final Answer:

   bg-blue-600 disabled:bg-gray-400 disabled:text-gray-300 text-white -> Option B

5. Quick Check:

   Disabled styles need disabled: prefix [OK]

Hint: Use disabled: prefix on all styles changing when disabled [OK]

Common Mistakes:

• Missing disabled: prefix on text color
• Placing disabled classes without prefix
• Mixing order causing style override issues