Animation mixin patterns in SASS - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

What is the output CSS of this Sass animation mixin usage?

Given the Sass code below, what CSS will be generated for the .box class?

SASS

@mixin fadeIn($duration) {
  animation-name: fadeIn;
  animation-duration: $duration;
  animation-fill-mode: forwards;
}

@keyframes fadeIn {
  from { opacity: 0; }
  to { opacity: 1; }
}

.box {
  @include fadeIn(2s);
}

A

.box {
  animation-name: fadeIn;
  animation-duration: 2s;
  animation-fill-mode: backwards;
}

B

.box {
  animation-name: fadeIn;
  animation-duration: 2;
  animation-fill-mode: forwards;
}

C

.box {
  animation-name: fadeIn;
  animation-duration: 2s;
  animation-fill-mode: forwards;
}

D

.box {
  animation-name: fadeOut;
  animation-duration: 2s;
  animation-fill-mode: forwards;
}

💡 Hint

Check how the mixin uses the $duration parameter and the animation-fill-mode property.

The mixin sets animation-name to fadeIn, animation-duration to the passed $duration (2s), and animation-fill-mode to forwards. Option C matches exactly.

🧠 Conceptual

intermediate

Which option correctly explains the benefit of using animation mixins in Sass?

Why do developers use animation mixins in Sass instead of writing animation CSS directly each time?

A They automatically optimize animations for all browsers without extra code.

B They allow reusing animation code with different parameters, reducing repetition and errors.

C They convert animations into JavaScript for better performance.

D They prevent animations from running on mobile devices by default.

💡 Hint

Think about how mixins help with writing CSS faster and cleaner.

Mixins let you write animation code once and reuse it with different values, saving time and avoiding mistakes. They don't automatically optimize or convert animations.

❓ selector

advanced

Which Sass selector usage correctly applies an animation mixin only on hover?

Given the mixin @mixin slideRight($time), which option applies it only when the user hovers over .menu-item?

SASS

@mixin slideRight($time) {
  animation-name: slideRight;
  animation-duration: $time;
  animation-fill-mode: forwards;
}

@keyframes slideRight {
  from { transform: translateX(0); }
  to { transform: translateX(100px); }
}

A

.menu-item {
  &:hover {
    @include slideRight(1s);
  }
}

B

.menu-item:hover {
  @include slideRight(1s);
}

C

.menu-item {
  @include slideRight(1s);
  &:hover {
    animation-play-state: paused;
  }
}

D

.menu-item:hover {
  animation-name: slideRight;
  animation-duration: 1s;
  animation-fill-mode: forwards;
}

💡 Hint

Consider Sass nesting and how mixins are included inside selectors.

Option A uses Sass nesting with &:hover inside .menu-item and includes the mixin correctly. Option A is plain CSS syntax, not Sass nesting. Option A applies animation always and pauses on hover. Option A writes CSS manually, not using the mixin.

❓ layout

advanced

How does using animation mixins affect CSS file size and maintainability?

Consider a large project with many animations. What is the main layout-related benefit of using animation mixins in Sass?

A They reduce CSS file size by generating only needed animation code and improve maintainability by centralizing animation logic.

B They increase CSS file size because mixins duplicate code everywhere they are included.

C They automatically convert animations into CSS Grid layouts.

D They force all animations to run simultaneously, improving layout speed.

💡 Hint

Think about how mixins help organize code and avoid repetition.

Mixins let you write animation code once and reuse it, so you avoid repeating code manually. This keeps CSS smaller and easier to update. They do not force animations to run together or convert to grid.

❓ accessibility

expert

Which Sass animation mixin pattern best supports users who prefer reduced motion?

How can you write a Sass animation mixin that respects users' system preference for reduced motion?

A

@mixin fadeInReduced($duration) {
  animation-name: fadeIn;
  animation-duration: $duration;
  animation-fill-mode: forwards;
  @media (prefers-reduced-motion: reduce) {
    animation-delay: 0s;
  }
}

B

@mixin fadeInReduced($duration) {
  animation-name: fadeIn;
  animation-duration: $duration;
  animation-fill-mode: forwards;
  @media (prefers-reduced-motion: reduce) {
    animation-play-state: paused;
  }
}

C

@mixin fadeInReduced($duration) {
  animation-name: fadeIn;
  animation-duration: $duration;
  animation-fill-mode: forwards;
  @media (prefers-reduced-motion: reduce) {
    animation-duration: 0s;
  }
}

D

@mixin fadeInReduced($duration) {
  @media (prefers-reduced-motion: reduce) {
    animation: none !important;
  }
  @media (prefers-reduced-motion: no-preference) {
    animation-name: fadeIn;
    animation-duration: $duration;
    animation-fill-mode: forwards;
  }
}

💡 Hint

Consider how to completely disable animations for users who want reduced motion.

Option D disables animation entirely with 'animation: none !important;' inside the reduced motion media query, which respects user preference. Other options only pause or shorten animation but do not fully disable it.