WRWEB ENGINEERING
REFORGING15 · 3/7
ALL LESSONS→WEEK 15→WEDNESDAY

CONSTRAIN · CSS TO THE FRONTIER

Transitions

CSS interaction and rendering30–60 MINUTESCORE + PRACTICAL
01

GROUND

Problem

What becomes confusing, fragile, or impossible without understanding transitions? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

CSS separated presentation from document structure, then grew from simple styling into a constraint-based layout and state language.
02

LEARN

Concept explanation

Transitions belongs to “CSS interaction and rendering”. transitions is learned by comparing readable, constrained, and deliberately clever implementations against same evidence.

For transitions, trace concrete input, state transition, output, and failure through a constraint system resolved through cascade, computed values, layout, paint, and compositing.

Rules enter a cascade; computed values feed layout; layout feeds paint and compositing. Every visual result has a traceable cause. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Observable

Evidence produced by the transitions experiment: output, state, trace, bytes, timing, or diagnostics.

Invariant

Condition that must remain true while inputs or implementation of transitions change.

Boundary

Point where transitions crosses ownership, representation, time, process, network, or trust.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Baseline · one variable

SETUPSolve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states.

OBSERVEAll versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost.

WHY IT MATTERSThis isolates the normal contract of transitions; preserve its raw evidence as the control for every later comparison.

Boundary · same contract, harder input

SETUPRun all three implementations against: Animate transform and layout property side-by-side.

OBSERVERecord what remains invariant and the first representation, owner, size, or timing value that changes in Chromium CSS panels · Rendering · print preview.

WHY IT MATTERSA boundary example is useful only when one named dimension changes and everything else stays comparable.

Failure · evidence before repair

SETUPForce every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.

OBSERVECapture the first divergence from the baseline, including exact input, diagnostic, state, and recovery result. Expected recovery: All versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost.

WHY IT MATTERSThe diagnostic is part of the interface. Repair the proven cause, not the most visible symptom.

Cross-layer · follow ownership

SETUPTrace transitions one layer below its usual abstraction through a constraint system resolved through cascade, computed values, layout, paint, and compositing.

OBSERVETrace winning declarations, computed values, box sizes, grid/flex tracks, paint, and layout shift.

WHY IT MATTERSThe lower layer is earned when it explains evidence the current layer cannot. Otherwise keep transitions at the simpler boundary.

03

SEE

Worked example

Start from supplied index.html. Focus: Solve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states.

  1. Run: Open index.html and inspect Styles, Computed, and layout overlays.
  2. Save baseline evidence. Trace winning declarations, computed values, box sizes, grid/flex tracks, paint, and layout shift.
  3. Boundary case: Run all three implementations against: Animate transform and layout property side-by-side.
  4. Failure case: Force every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.
RESULT
All versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost. Starter-level baseline: Two bordered cases form responsive columns and collapse naturally when available inline size becomes too small.
04

START HERE

Starter material

PREREQUISITESA modern browser with Elements, Styles, Computed, and layout inspection panels.

ONE-TIME SETUPCreate an empty folder, save starter as index.html, then use browser File → Open File to open it.

Create index.html, paste this exact content, then run the command below.

<!doctype html>
<meta charset="utf-8">
<title>transitions</title>
<style>
  * { box-sizing: border-box }
  body { margin: 0; font: 16px system-ui }
  .lab { display: grid; grid-template-columns: repeat(auto-fit, minmax(12rem, 1fr)); gap: 1rem; padding: 1rem }
  .case { border: 2px solid; padding: 1rem }
</style>
<main class="lab"><article class="case"><h1>transitions</h1><p>Baseline case</p></article><article class="case">Comparison case</article></main>
RUNOpen index.html and inspect Styles, Computed, and layout overlays.

STOP / CLEANUPClose the browser tab when finished; keep index.html as evidence.

05

DO WITH GUIDANCE

Guided exercise

Solve under constraint: transitions

  1. Normal case: Solve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states.
  2. Write predicted evidence from this named case before running starter.
  3. Keep readable baseline, then remove one convenience without hiding behavior.
  4. Run exact normal case. Save commands, inputs, outputs, and diagnostics in notebook.
  5. Explain changed evidence using lesson mental model in no more than five sentences.
Concrete guided solution
  1. Copy the supplied index.html unchanged and run: Open index.html and inspect Styles, Computed, and layout overlays.
  2. Write this prediction before inspecting output: All versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost.
  3. Perform only the named normal case: Solve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states.
  4. Save the raw output, then annotate input → transition → evidence. Use Chromium CSS panels · Rendering · print preview to confirm the transition rather than inferring it.
  5. Compare prediction with evidence; if they differ, keep both and write the rule that explains the difference. Reference baseline: Two bordered cases form responsive columns and collapse naturally when available inline size becomes too small.
06

DO ALONE

Independent exercise

Compare three versions: transitions

  1. Create second case from blank file: Run all three implementations against: Animate transform and layout property side-by-side.
  2. Then create controlled failure: Force every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.
  3. Use Chromium CSS panels · Rendering · print preview to prove behavior, then repair controlled failure.
  4. Compare result against supplied acceptance checks and reference approach before marking complete.
Concrete independent solution
  1. Duplicate the starter into a clean comparison case; change only this boundary: Run all three implementations against: Animate transform and layout property side-by-side.
  2. Save its evidence beside the baseline and identify the first changed value. Trace winning declarations, computed values, box sizes, grid/flex tracks, paint, and layout shift.
  3. Create the exact controlled failure: Force every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.
  4. Version A: use clearest native primitives and name every intermediate state for transitions.
  5. Version B: remove one convenience while preserving same input/output contract.
  6. Version C: compress only after A and B pass baseline: Implement focus-visible, target, checked, and reduced-motion states.
  7. Run shared boundary and failure fixtures against all versions: Animate transform and layout property side-by-side. / Create stacking-context surprise and diagnose with layer/paint tools.
  8. Keep A unless another version has measured benefit; expected invariant: Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.
  9. Rerun baseline, boundary, and repaired failure together. Accept only if all reproduce: All versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost.
07

COMPARE

Expected result

  • All versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost.
  • Two bordered cases form responsive columns and collapse naturally when available inline size becomes too small.
  • Controlled transitions failure produces captured evidence; repair restores stated invariant without hiding error.
08

PROVE

Acceptance checks

Lesson is complete only when every check is true. Each check is stored locally and travels with your JSON backup.

0/5 complete · saved on this device

09

UNSTICK

Hints

Reveal hints
  1. Start with supplied normal case exactly as written: Solve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states.
  2. For boundary case, change only named dimension: Run all three implementations against: Animate transform and layout property side-by-side.
  3. If result is confusing, diff raw inputs and evidence before editing implementation.
  4. If tool shows nothing useful, move observation one boundary lower: representation, runtime, OS, or network.
10

VERIFY

Solution

Attempt both exercises before opening reference approach.

Reveal reference solution
  1. Run unmodified starter and preserve baseline evidence: Two bordered cases form responsive columns and collapse naturally when available inline size becomes too small.
  2. Version A: use clearest native primitives and name every intermediate state for transitions.
  3. Version B: remove one convenience while preserving same input/output contract.
  4. Version C: compress only after A and B pass baseline: Implement focus-visible, target, checked, and reduced-motion states.
  5. Run shared boundary and failure fixtures against all versions: Animate transform and layout property side-by-side. / Create stacking-context surprise and diagnose with layer/paint tools.
  6. Keep A unless another version has measured benefit; expected invariant: Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.
11

PREDICT · INSPECT · BREAK · DEBUG · MEASURE

Interrogate reality

Prediction: write expected output, state transition, ordering, and failure evidence before running either exercise.

Inspection: Use Styles, Computed, box model, Grid/Flex overlays, animation tools, paint flashing, and layer inspection.

Measurement: Measure stylesheet size, style recalculation, layout, paint, cumulative shift, and responsive failure points.

INSPECT

Capture raw evidence before explaining.

BREAK

Change one assumption and force controlled failure.

DEBUG

Find cause with Chromium CSS panels · Rendering · print preview before editing fix.

TOOL DRILL · keyboard only · record one retrievable command or shortcut
12

MASTERY + FRONTIER + BOUNDARY

Own the knowledge

TEACH

Explain transitions at beginner, intermediate, and senior depth.

REBUILD

Recreate smallest useful example from blank file without notes or AI.

RETRIEVE

Schedule recall for day 1, 7, 30, and 90.

Creative frontier lab

Try first without opening the solutions. The constraints invite invention; the reference gives one concrete direction, never the only valid answer.

Constraint inversion

Re-solve transitions by removing the most convenient abstraction. make content and container constraints choose the layout without viewport breakpoints.

CONSTRAINTKeep the same inputs, observable result, and failure evidence; change the means, not the contract.

ORIGINAL IDEATurn subtraction into a design tool: the missing abstraction should reveal which responsibility it used to hide.

Reveal frontier solution
  1. Freeze the contract as three fixtures: Solve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states. / Run all three implementations against: Animate transform and layout property side-by-side. / Force every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.
  2. List every convenience used by the starter; remove the highest-level one while preserving Open index.html and inspect Styles, Computed, and layout overlays..
  3. Implement the smallest replacement using make content and container constraints choose the layout without viewport breakpoints.
  4. Run all fixtures and compare raw evidence. Keep the simpler version unless the removed abstraction has a demonstrated benefit.
Representation x-ray

Build an explanation artifact for transitions: annotate winning declarations, computed values, constraint sizes, paint, and compositing.

CONSTRAINTA peer must be able to locate the first divergence without reading implementation code.

ORIGINAL IDEATreat the explanation itself as a product: make invisible transitions visible, replayable, and diffable.

Reveal frontier solution
  1. Create one row or timestamped event for each transition in: Solve transitions three ways using identical fixture: Implement focus-visible, target, checked, and reduced-motion states.
  2. For every row record input, representation, owner, operation, output, and tool evidence from Chromium CSS panels · Rendering · print preview.
  3. Replay Run all three implementations against: Animate transform and layout property side-by-side.; highlight only changed rows.
  4. Replay Force every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.; stop at the first divergent row and attach its recovery action.
Adversarial remix

Combine the boundary and failure into a new user-visible scenario for transitions. design one component that survives missing content, long tokens, zoom, print, and reduced motion.

CONSTRAINTDo not merely add more input. Invent a recovery interaction, alternate representation, or self-checking behavior.

ORIGINAL IDEAMake the system teach its own limits: the artifact should expose the invariant and offer a safe next action when it breaks.

Reveal frontier solution
  1. Combine these two pressures without changing them: Run all three implementations against: Animate transform and layout property side-by-side. AND Force every implementation through: Create stacking-context surprise and diagnose with layer/paint tools.
  2. Name the invariant that must survive and the user-visible evidence when it cannot: All versions preserve Keyboard focus remains visible; reduced motion works; trace distinguishes compositor-friendly and layout-triggering work.; comparison records code size, predictability, and debugging cost.
  3. Implement this original direction: design one component that survives missing content, long tokens, zoom, print, and reduced motion.
  4. Demonstrate baseline, combined failure, recovery, then baseline again; save the sequence as a regression fixture.

Capability frontier

Push transitions until another layer becomes justified. Record one robust technique, one contextual trade-off, and one labeled hack or historical curiosity.

CORE · PRACTICAL · CONTEXTUAL · HACK · FRAGILE · HISTORICAL · GOLF

Boundary

CSS expresses presentation and limited state; arbitrary data transformation and durable application logic belong elsewhere.

If this vanished tomorrow…

Rely on semantic document order, browser defaults, presentational attributes only as historical context, and simpler layouts.

Why next layer is earned

JavaScript is earned when the document needs computation and interaction beyond native HTML and CSS state.