KodingKaro
CSS · Advanced · Cascade, Inheritance, and Specificity

The cascade and inheritance

When multiple rules could style one property, the cascade determines which value is used. Inheritance passes selected values from ancestors to descendants.

✓ What you will learn in this topic

  • Explain the key idea: Inheritance shares selected values, while the cascade resolves competing declarations.
  • Apply the concept: The link inherits its text color from the demo, and the card border follows the component’s current text color.
  • Avoid this common mistake:

Concept explanation

The cascade considers origin, importance, cascade layer, specificity, and source order. Not every property inherits: text color often does, while margin does not. Inherited values are convenient for shared text styles, but component boundaries should remain intentional.

Browser developer tools show matched declarations and crossed-out losing rules. Inspect those before adding another override.

Syntax

A CSS rule has a selector followed by declarations. Each declaration is a property and a value; the braces group the declarations that apply to matching elements.

.demo {
  color: #334155;
}
.demo a {
  color: inherit;
}

Example 1: a small page element

Use this HTML as the target and place the CSS in a stylesheet linked to the page, or inside a <style> element while experimenting.

<main class="demo card-grid course-grid dashboard-panel course-card-list dashboard-grid card-layout"><h2>Learning card</h2><p>Clear styles make this information easier to scan.</p><nav class="site-nav"><a href="/learn">Courses</a></nav><label class="form-field"><span>Email</span><input type="email" aria-invalid="true"></label><article class="card course-card dashboard-card theme-dark"><span class="badge status">New</span><div class="course-card__image"></div><h2 class="course-card__title card__title">Course update</h2><p class="status">New lessons are available this week.</p><a href="/learn" aria-current="page">Read the details</a><div class="actions course-card__actions dashboard-panel__actions"><button type="button">View lessons</button><button type="button" disabled>Unavailable</button></div></article></main>
.demo {
  color: #334155;
}
.demo a {
  color: inherit;
}

Expected result: The link inherits its text color from the demo, and the card border follows the component’s current text color.

Example 2: a practical interface card

The same idea can style a reusable card on a course page. The class selector keeps the rule attached to this component rather than changing every element of that type.

<section class="demo card-grid course-grid dashboard-panel course-card-list dashboard-grid card-layout"><h2>Learning card</h2><p>Clear styles make this information easier to scan.</p><nav class="site-nav"><a href="/learn">Courses</a></nav><label class="form-field"><span>Email</span><input type="email" aria-invalid="true"></label><article class="card course-card dashboard-card theme-dark"><span class="badge status">New</span><div class="course-card__image"></div><h2 class="course-card__title card__title">Course update</h2><p class="status">New lessons are available this week.</p><a href="/learn" aria-current="page">Read the details</a><div class="actions course-card__actions dashboard-panel__actions"><button type="button">View lessons</button><button type="button" disabled>Unavailable</button></div></article></section>
.theme {
  font-family: system-ui, sans-serif;
  color: #172033;
}
.card {
  border-color: currentColor;
}

Expected result: The course update reads as a distinct interface card, and its content follows the spacing, color, and layout choices in the rule.

Common mistake

Adding !important to every conflict hides the real cascade and makes future changes harder.

Best practice

Inspect matched rules, reduce unnecessary specificity, and use source order intentionally.

Practice exercise

Given two competing component rules, predict the winner, then refactor the selectors so their intended priority is clear. Apply it to the example above and inspect the result at a narrow and a wide viewport.

Section summary

  • Inheritance shares selected values, while the cascade resolves competing declarations.
  • Inspect matched rules, reduce unnecessary specificity, and use source order intentionally.

Knowledge check

What is inheritance in CSS?

Reveal the explanation

Inheritance applies to selected properties; margin and padding do not automatically inherit.

Finish the module lessons, then take the server-scored module quiz to check your understanding.

Practical example

css
.demo {
  color: #334155;
}
.demo a {
  color: inherit;
}

Expected result:

The link inherits its text color from the demo, and the card border follows the component’s current text color.

Hands-on practice task

Given two competing component rules, predict the winner, then refactor the selectors so their intended priority is clear.

In this section

Other lessons in Cascade, Inheritance, and Specificity

Broaden your knowledge

Related learning topics