State class generation (hover, active, disabled) in SASS

Introduction

State classes help change how buttons or links look when you hover, click, or disable them. This makes websites easier to use and understand.

You want a button to change color when someone moves their mouse over it.

You want a link to look pressed when clicked.

You want to show a button as disabled so users know it can't be clicked.

You want consistent styles for interactive elements across your site.

You want to write less code by generating these states automatically.

Syntax

SASS

@mixin state-classes($base-class) {
  .#{$base-class} {
    &:hover {
      // hover styles here
    }
    &:active {
      // active styles here
    }
    &.disabled, &[disabled] {
      // disabled styles here
      pointer-events: none;
      opacity: 0.5;
    }
  }
}

The @mixin helps create reusable style blocks.

Use & to refer to the current selector inside nested rules.

Examples

This mixin creates hover, active, and disabled states for a class you provide.

SASS

@mixin state-classes($base-class) {
  .#{$base-class} {
    &:hover {
      background-color: lightblue;
    }
    &:active {
      background-color: blue;
      color: white;
    }
    &.disabled, &[disabled] {
      opacity: 0.5;
      pointer-events: none;
    }
  }
}

This applies the state styles to elements with the class btn.

SASS

@include state-classes('btn');

Basic button styles before states are added.

SASS

.btn {
  background-color: gray;
  color: black;
  padding: 0.5rem 1rem;
  border-radius: 0.25rem;
  cursor: pointer;
}

Sample Program

This code creates a mixin to add hover, active, and disabled states to a button class. Then it includes the mixin for the btn class and sets basic button styles. The button changes color on hover and active, and looks faded and unclickable when disabled.

SASS

@mixin state-classes($base-class) {
  .#{$base-class} {
    &:hover {
      background-color: lightblue;
    }
    &:active {
      background-color: blue;
      color: white;
    }
    &.disabled, &[disabled] {
      opacity: 0.5;
      pointer-events: none;
      cursor: not-allowed;
    }
  }
}

@include state-classes('btn');

.btn {
  background-color: gray;
  color: black;
  padding: 0.5rem 1rem;
  border-radius: 0.25rem;
  cursor: pointer;
  user-select: none;
  transition: background-color 0.3s ease, color 0.3s ease, opacity 0.3s ease;
}

Important Notes

Use pointer-events: none; on disabled states to prevent clicks.

Adding cursor: not-allowed; helps users see the button is disabled.

Transitions make state changes smooth and nicer to see.

Summary

State classes help show different looks for hover, active, and disabled states.

Use a Sass mixin to create these states easily for any class.

Disabled states should prevent clicks and show a faded look.

Practice

1. What is the main purpose of using state classes like :hover, :active, and .disabled in Sass?

easy

A. To change the appearance of elements based on user interaction or status

B. To add animations to elements automatically

C. To create new HTML elements dynamically

D. To load external CSS files conditionally

Solution

1. Step 1: Understand state classes

   State classes like :hover and :active change how elements look when users interact with them.

2. Step 2: Identify their purpose

   They help show different styles for hover, active, or disabled states to improve user experience.

3. Final Answer:

   To change the appearance of elements based on user interaction or status -> Option A

4. Quick Check:

   State classes change look on interaction [OK]

Hint: State classes show style changes on user actions [OK]

Common Mistakes:

• Thinking state classes create new elements
• Confusing state classes with animations
• Believing state classes load files

2. Which of the following is the correct Sass syntax to create a mixin for hover and active states?

easy

A. @mixin states { :hover { color: blue; } :active { color: red; } }

B. @mixin states { &:hover { color: blue; } &:active { color: red; } }

C. @mixin states { .hover { color: blue; } .active { color: red; } }

D. @mixin states { hover { color: blue; } active { color: red; } }

Solution

1. Step 1: Review Sass mixin syntax

   Mixins use @mixin name { ... } and nested selectors use &:state for pseudo-classes.

2. Step 2: Check correct pseudo-class usage

   Correct syntax uses &:hover and &:active inside the mixin.

3. Final Answer:

   @mixin states { &:hover { color: blue; } &:active { color: red; } } -> Option B

4. Quick Check:

   Use & with :hover and :active in mixins [OK]

Hint: Use & before pseudo-classes inside mixins [OK]

Common Mistakes:

• Omitting & before pseudo-classes
• Using class selectors instead of pseudo-classes
• Missing @mixin keyword

3. Given this Sass code, what color will the button text be when hovered?

@mixin states {
  &:hover { color: green; }
  &:active { color: orange; }
  &.disabled { color: gray; cursor: not-allowed; }
}

.button {
  color: black;
  @include states;
}

medium

A. Green

B. Black

C. Orange

D. Gray

Solution

1. Step 1: Understand the mixin states

   The mixin sets color: green on :hover, color: orange on :active, and gray with disabled class.

2. Step 2: Check the hover state

   When the button is hovered, the :hover style applies, changing text color to green.

3. Final Answer:

   Green -> Option A

4. Quick Check:

   Hover changes color to green [OK]

Hint: Hover state color overrides base color [OK]

Common Mistakes:

• Confusing active color with hover color
• Ignoring the disabled class
• Assuming base color stays on hover

4. Identify the error in this Sass code that tries to create disabled state styles:

@mixin states {
  &:hover { color: blue; }
  &:active { color: red; }
  &:disabled { color: gray; cursor: not-allowed; }
}

.button {
  @include states;
}

medium

A. Cannot use mixins inside class selectors

B. Missing semicolon after color: red

C. Using &:disabled instead of &.disabled for disabled class

D. Mixin name should be capitalized

Solution

1. Step 1: Check pseudo-class vs class usage

   :disabled is a pseudo-class for form elements, but here disabled is a class, so &.disabled is correct.

2. Step 2: Verify other syntax

   Semicolons are present, mixin naming is flexible, and mixins can be used inside classes.

3. Final Answer:

   Using &:disabled instead of &.disabled for disabled class -> Option C

4. Quick Check:

   Use .disabled class selector, not :disabled pseudo-class [OK]

Hint: Use .disabled class, not :disabled pseudo-class [OK]

Common Mistakes:

• Confusing :disabled pseudo-class with .disabled class
• Forgetting semicolons
• Thinking mixins need capital letters

5. You want to create a reusable Sass mixin that adds hover, active, and disabled states to any button. The disabled state should make the button look faded and prevent clicks. Which of these mixins correctly implements this behavior?

hard

A. @mixin button-states {
&:hover { background-color: lightblue; }
&:active { background-color: blue; }
&.disabled { opacity: 1; pointer-events: auto; cursor: not-allowed; }
}

B. @mixin button-states {
&:hover { background-color: lightblue; }
&:active { background-color: blue; }
&:disabled { opacity: 0.5; pointer-events: none; cursor: not-allowed; }
}

C. @mixin button-states {
&:hover { background-color: lightblue; }
&:active { background-color: blue; }
&.disabled { opacity: 0.5; cursor: default; }
}

D. @mixin button-states {
&:hover { background-color: lightblue; }
&:active { background-color: blue; }
&.disabled { opacity: 0.5; pointer-events: none; cursor: not-allowed; }
}

Solution

1. Step 1: Check disabled state styling

   The disabled state should fade the button with opacity: 0.5 and prevent clicks using pointer-events: none.

2. Step 2: Verify cursor and selector usage

   Using &.disabled is correct for a class. Cursor should be not-allowed to show disabled status.

3. Step 3: Compare options

   @mixin button-states { &:hover { background-color: lightblue; } &:active { background-color: blue; } &.disabled { opacity: 0.5; pointer-events: none; cursor: not-allowed; } } correctly uses &.disabled, sets opacity to 0.5, disables pointer events, and sets cursor properly.

4. Final Answer:

   @mixin button-states { &:hover { background-color: lightblue; } &:active { background-color: blue; } &.disabled { opacity: 0.5; pointer-events: none; cursor: not-allowed; } } -> Option D

5. Quick Check:

   Disabled state fades and disables clicks with pointer-events none [OK]

Hint: Use pointer-events:none and opacity for disabled state [OK]

Common Mistakes:

• Using :disabled pseudo-class instead of .disabled class
• Not disabling pointer events on disabled
• Setting opacity to 1 in disabled state