← All posts

What CSS is still missing in 2026

State of CSS, layout gaps, centering, declarative partial updates, and how AI reshapes site value.

Tags
cssNewsweb platform
Contents

In brief

Frontend Focus #743 threads several stories: Temani Afif refreshes centering with place-content and anchor positioning, State of CSS 2026 opens, Patrick Brosset maps layout gaps from last year’s survey, and Kevin Powell asks how AI summaries and scraping change the economics of websites. Platform news covers Chrome 148, WordPress 7.0, and a <input type="number"> bug.

What happened

Centering in 2026 is not just “flex by feel.” Modern patterns lean on place-content, logical properties, and CSS anchor positioning to tie elements to anchors without heavy JavaScript. State of CSS 2026 trims the feature list on purpose — fewer checkboxes, more meaningful capabilities — a response to an era where part of the code is AI-assisted.

Patrick Brosset reads layout friction through survey data: grid and flex closed many gaps, but complex UI patterns still push teams toward custom logic. Kevin Powell, post-Google I/O, asks what happens when users get answers in summaries without clicking — and what that means for frontend and SEO.

Brief news: WordPress 7.0 with optional AI features; Chrome fixes unexpected value changes on <input type="number"> (Chrome 150); Jake Archibald documented the bug; Vivaldi ships a major redesign; asm.js leaves Firefox; Chrome 148 (flagged) adds declarative partial updates: <template for> and setHTML() / streamHTML() for streaming HTML without rebuilding the whole tree.

Manuel Matuzovic warns that aria-label on a bare <div> violates spec and behaves inconsistently in screen readers — prefer semantic elements or explicit roles.

Why it matters

CSS moves faster than textbooks. Anchor positioning and declarative updates shift work from JS to the platform — but only if browsers and polyfills match your baseline.

State of CSS is not academic: it shows which APIs reach production versus slide-deck-only. The “AI kills websites” thread is product economics, but for engineers it signals that solid layout and accessibility stay differentiators when aggregators devalue raw text.

In practice

  1. Revisit centering with place-content and logical axes — fewer magic margins.
  2. Track anchor positioning for popovers and tooltips without positioning libraries.
  3. Do not slap aria-label on <div> for convenience — fix semantics.
  4. Experiment with <template for> behind Chrome 148 flags for list-heavy UI.
  5. Take State of CSS 2026 so your team marks what you actually ship.

Takeaway

CSS in 2026 is not “more flex tweaks” — it is new layout primitives and declarative DOM updates. Context shifts too: AI pressure on classic articles rises, while engineering-quality markup and platform APIs remain visible to users.