CSS basics · Lesson 12 of 12 · 10 minutes

CSS basics: Cascade review

With equal origin, importance, layer, and specificity, a later declaration wins for the same property.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build cascade review
Build this first target: p with color: #58626b. Keep the selector relationships intact and inspect the preview.
Hint & worked example
With equal origin, importance, layer, and specificity, a later declaration wins for the same property.
The requested selectors and declarations exist outside comments.
```
p { color: #58626b; }
```
Common mistake to avoid: If the page fits one desktop viewport, no narrower viewport needs checking.
2
Extend the cascade review example
Extend your file to include: p with color: #58626b; p with color: #182b2a. Keep the selector relationships intact and inspect the preview.
Hint & worked example
With equal origin, importance, layer, and specificity, a later declaration wins for the same property.
The requested selectors and declarations exist outside comments.
```
p { color: #58626b; }
p { color: #182b2a; }
```
Common mistake to avoid: Hiding all overflow always makes content accessible.
3
Verify the complete cascade review pattern
Finish the pattern with: p with color: #58626b; p with color: #182b2a; p with line-height: 1.6. Keep the selector relationships intact and inspect the preview.
Hint & worked example
With equal origin, importance, layer, and specificity, a later declaration wins for the same property.
The requested selectors and declarations exist outside comments.
```
p { color: #58626b; }
p { color: #182b2a; }
p { line-height: 1.6; }
```
Common mistake to avoid: If the page fits one desktop viewport, no narrower viewport needs checking.

Understand the pattern

With equal origin, importance, layer, and specificity, a later declaration wins for the same property.

Misconceptions to reject

If the page fits one desktop viewport, no narrower viewport needs checking.
Hiding all overflow always makes content accessible.

The preview is a sanitized subset, not a full browser compatibility test.

Worked example and expected result

p { color: #58626b; }
p { color: #182b2a; }
p { line-height: 1.6; }

With equal origin, importance, layer, and specificity, a later declaration wins for the same property.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains cascade review?If the page fits one desktop viewport, no narrower viewport needs checking.Hiding all overflow always makes content accessible.With equal origin, importance, layer, and specificity, a later declaration wins for the same property.

Apply it elsewhere

You reuse cascade review in a different project. What must still be verified?Only whether the source code has the same number of lines.The resulting layout, focus behavior, and readability at the target viewport sizes.Nothing; passing a single exercise guarantees every future use.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Review this course Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

01CSS basics: Focus-visible statesKeyboard focus needs a visible indicator. focus-visible can provide one without relying on hover.Practice

MDN: CSS styling