CSS Pseudo-classes

Introduction

Pseudo-classes target elements in a specific state or position — hovered, focused, first-child, the third checkbox checked. They're how CSS becomes interactive.

Business problem

Business pressure: Product teams need CSS pseudo-classes implemented consistently — layout regressions, WCAG failures, and LCP/CLS cliffs on Shopify-scale surfaces directly hit conversion and brand trust.

• Conversion: Visual polish and render performance on CSS pseudo-classes surfaces affect checkout and signup funnels at Material Design.
• Brand: Inconsistent CSS pseudo-classes fragments Polaris design-system contracts across squads.
• Velocity: CSS debt around CSS pseudo-classes slows every feature team — staff engineers treat styling as platform infrastructure.

Why this feature exists

Platform history: CSS standardized CSS pseudo-classes so authors could separate presentation from HTML without table-layout hacks or per-element JavaScript layout engines.

• Problem solved: Declarative, cacheable styling for CSS pseudo-classes across entire sites and design systems.
• Rejected alternative: Inline styles and JS layout — unmaintainable at Shopify product scale.

Browser rendering perspective

Rendering impact: CSS Pseudo-classes touches the style → layout → paint → composite pipeline differently per engine when CSS pseudo-classes rules change.

• Chrome (Blink): Style invalidation → LayoutNG → Paint → Viz compositor; properties used in CSS pseudo-classes may trigger layout-only or paint-only invalidation.
• Firefox (Gecko): Servo Stylo resolves cascade; WebRender composites — subpixel CSS pseudo-classes rounding can differ from Blink.
• Safari (WebKit): WebKit style resolver + GPU layer rules; CSS pseudo-classes bugs often surface only on iOS Safari — validate on real devices.

Internal browser workflow

Workflow: DOM + CSSOM → selector matching for CSS pseudo-classes rules → cascade/specificity → computed values → layout tree → paint → composite.

• Matching cost: Overly broad selectors for CSS pseudo-classes increase style recalc on large Material Design product DOMs.
• Cascade: Source order, specificity, and inheritance pick winning CSS pseudo-classes declarations.
• DevTools: Computed tab shows final CSS pseudo-classes values — diff across Chrome, Firefox, and Safari.

Feature deep dive

Categories:

• State — :hover, :focus, :focus-visible, :active, :disabled.
• Position — :first-child, :last-child, :nth-child(2n), :only-child.
• Form — :checked, :valid, :invalid, :placeholder-shown.
• Logical — :not(.x), :is(h1, h2), :has(img).

Examples

Modern :has() lets a parent style itself based on its children:

.card:has(img) { padding: 0; }      /* cards with images go edge-to-edge */
label:has(input:checked) { color: #4f46e5; font-weight: 600; }

Real-world use

Form validation hints show up automatically with input:invalid:not(:placeholder-shown) — only invalid AND only after the user typed.

Real production example

Production: Shopify, Material Design, and Shopify codify CSS pseudo-classes via design tokens, Stylelint, visual regression CI, and component prop APIs aligned with Polaris.

• Pattern: Token-driven CSS pseudo-classes with Percy/Chromatic snapshots on every PR.
• Observability: CrUX/RUM tie CSS pseudo-classes changes to LCP and CLS on high-traffic templates.
• Contract: Design system documents allowed values — no rogue hex in product CSS.

Enterprise use case

Enterprise: Polaris, Carbon, and Material Design encode CSS pseudo-classes in multi-brand token pipelines, dark mode, and white-label tenant themes.

• Component APIs: Apps consume CSS pseudo-classes via tokens and props — not ad-hoc stylesheets.
• CI gates: axe, contrast checks, and Coverage audits block CSS pseudo-classes regressions before merge.
• Migration: Legacy CSS pseudo-classes refactors use codemods plus visual diff baselines.

Accessibility considerations

A11y: CSS pseudo-classes must not remove focus visibility, break 200% zoom, convey state by color alone, or hide content from assistive technology (WCAG 2.2).

• Focus: :focus-visible + outline — never naked outline: none.
• Contrast: Verify CSS pseudo-classes color choices meet 4.5:1 on Material Design checkout and form flows.
• Motion: Gate CSS pseudo-classes animations behind prefers-reduced-motion.

Performance considerations

Performance: CSS pseudo-classes can trigger reflow, expensive selectors, compositor layer explosion, or unused CSS bloat — profile with DevTools Performance and Coverage.

• Animation: Animate transform/opacity for CSS pseudo-classes — avoid layout-thrashing properties.
• Selectors: Deep chains for CSS pseudo-classes slow style recalc on Shopify-size pages.
• Payload: Purge unused CSS pseudo-classes rules in production bundles (Tailwind JIT, PurgeCSS).

SEO considerations

SEO: CSS pseudo-classes affects LCP, CLS, and mobile usability — Google Core Web Vitals and readable above-the-fold content are ranking signals.

• LCP: CSS pseudo-classes on hero type and images determines largest contentful paint timing.
• CLS: Reserve space with sizing (CSS pseudo-classes) before fonts and images load.
• Mobile: Readable CSS pseudo-classes at 320px — Material Design mobile-first baseline.

Scalability considerations

Scale: CSS pseudo-classes choices compound across micro-frontends, A/B skins, dark mode, and Material Design multi-tenant white-label themes.

• Tokens: Centralize CSS pseudo-classes in custom properties — not magic numbers per squad.
• Specificity: Flat selectors scale better than nested wars across dozens of teams.
• Theming: Polaris and Carbon theme switches depend on consistent CSS pseudo-classes architecture.

Common production issues

Production failures: Specificity overrides, Safari-only CSS pseudo-classes glitches, stacking contexts, and breakpoints that pass Chrome CI but fail iOS WebKit.

• Cross-browser: Subpixel CSS pseudo-classes differs Blink vs WebKit — test real Safari.
• Regression: Global token change breaks unrelated CSS pseudo-classes — visual CI catches it.
• Third-party: Widget CSS collides with app CSS pseudo-classes — namespace or Shadow DOM.

Debugging guide

Debug: Chrome DevTools Elements (Styles + Computed), Layout/Flex/Grid overlays; Firefox layout tools; Safari Web Inspector on device.

• Overrides: Crossed-out CSS pseudo-classes rules — trace specificity winner.
• Box model: Inspect margin/padding/border when CSS pseudo-classes layout surprises.
• Coverage: Find dead CSS pseudo-classes CSS bloating bundles.

/* DevTools workflow — pseudo-classes */
1. Elements → select target node
2. Computed → filter relevant properties
3. Layout → box model + flex/grid overlay
4. Performance → record scroll/interaction

Best practices

• Use :focus-visible for keyboard-only focus rings.
• Use :is() to keep selector lists DRY.

Anti-patterns

• Inline styles: CSS pseudo-classes via style="" — unmaintainable at Shopify scale.
• !important wars: Fixing CSS pseudo-classes with specificity nukes instead of architecture.
• Magic numbers: Random px for CSS pseudo-classes outside the spacing/type token scale.

Trade-offs

• Utility vs components: Tailwind velocity vs Carbon-style token components for CSS pseudo-classes.
• Reset vs normalize: Predictable CSS pseudo-classes baseline vs faster initial ship.
• Pure CSS vs JS: CSS pseudo-classes without JavaScript until touch/a11y needs progressive enhancement.

Architecture review questions

• Which CSS pseudo-classes properties trigger layout vs paint vs composite-only updates?
• How does this CSS pseudo-classes choice affect WCAG contrast and keyboard focus visibility?
• What happens to CSS pseudo-classes under dark mode and Polaris design tokens?
• Where could CSS pseudo-classes cause CLS or LCP regression on Material Design templates?
• How would you debug overridden CSS pseudo-classes rules in production?
• What is the migration path for CSS pseudo-classes across 20 micro-frontends?

Interview questions

Hands-on exercise

Exercise: Implement CSS pseudo-classes on a component using Polaris spacing tokens — pass axe, Lighthouse ≥ 90, and Percy snapshots on mobile + desktop.

• Deliverable: PR with CSS pseudo-classes CSS, token references, before/after screenshots.
• Verify: Keyboard-only nav, 200% zoom, prefers-reduced-motion.
• Stretch: ADR for CSS pseudo-classes token naming in your design system.

Staff engineer notes

• Rendering lens: Classify every CSS pseudo-classes property as layout, paint, or composite — animate composite-safe properties only.
• Platform lens: CSS pseudo-classes belongs in the design-system layer; product teams consume tokens.
• Measurement lens: Tie CSS pseudo-classes changes to CrUX LCP/CLS on Material Design — CSS is revenue infrastructure.

Common pitfalls

• :has() isn't supported in older browsers — check caniuse.

Try it yourself

Edit the CSS panel — the preview updates live. Use DevTools Performance and Accessibility panels to validate.

Summary

CSS Pseudo-classes is core CSS engineering. Staff engineers evaluate CSS pseudo-classes through browser pipelines (Blink, Gecko, WebKit), WCAG 2.2, and design-system contracts (Material Design, Polaris, Carbon) — scaling across Shopify-class product surfaces without layout or accessibility debt.

Key takeaways

• Pseudo-classes target state, position, and form validity.
• :has() is the new game-changer — parents can react to children.