Notes from the edge of the web
Lookoutrakivaro
Dispatch · The open web · Updated January 2026

What Browsers Learn Next

The quietest revolutions on the web arrive as specifications. Here is what has landed, what is landing, and what still needs patience.

How a feature becomes ordinary

New web capabilities are drafted in public, mostly at the W3C and the WHATWG, where browser engineers, developers and accessibility experts argue over details for months or years. A feature is only useful to most of us once all the major engines (Chromium, WebKit and Gecko) ship it in a compatible way.

Two efforts have made that moment easier to see. The annual Interop project, a collaboration between browser makers, picks focus areas and measures progress with shared tests. And Baseline, maintained through the W3C's WebDX community group, labels features as "newly available" once they work in all core browsers and "widely available" roughly thirty months later. We borrow that vocabulary below.

Status table

Features we are tracking

Statuses reflect our reading of MDN and Baseline at the time of writing. Support changes quickly; always confirm on MDN or Can I use before relying on a feature.

FeatureWhat it unlocksStatusOur note
CSS container queriesComponents respond to the size of their containerWidely availableUse freely; the biggest layout shift since flexbox.
CSS :has()Style a parent based on what it containsWidely availableReplaces many small scripts.
CSS nestingNest rules natively, as in preprocessorsWidely availableOne less reason for a build step.
Passkeys (WebAuthn)Phishing-resistant sign-in without passwordsWidely availableSupported across major platforms and password managers.
Popover APIAccessible menus and overlays in plain HTMLNewly availableHandles focus and light-dismiss for you.
View Transitions (same-document)Animated changes between UI statesNewly availableCross-document transitions are still rolling out.
WebGPUModern GPU graphics and compute in the browserArrivingShipped in Chrome first; Safari and Firefox support is expanding by platform.
CSS anchor positioningTether tooltips and menus to any elementLimitedNot yet in every engine; use with a fallback.
Speculation Rules APIPrerender likely next pages for near-instant loadsLimitedChromium only; harmless to add as progressive enhancement.

Three shifts hiding in the table

The platform is absorbing the toolchain

Nesting, container queries, :has() and native popovers each replace something developers once needed a library or preprocessor for. The result is that a well-made site can again be a few plain files, as this one is. That lowers the barrier for the kind of single-author experiments we celebrate on our sites page.

The browser is becoming a serious compute platform

WebGPU, together with WebAssembly, makes it realistic to run image processing, simulations and even modest machine-learning models directly in a tab. Projects such as Transformers.js and WebLLM already demonstrate language models running client-side, with no data sent to a server.

Security is getting friendlier

Passkeys, built on the FIDO Alliance's standards and the W3C's WebAuthn specification, replace shared secrets with device-bound cryptographic keys. For ordinary users the change feels like convenience; underneath, it removes the most common route for phishing.

Field noteA practical rule: if a feature is "newly available", ship it as an enhancement with a sensible fallback. If it is "widely available", you can usually just use it.
Next dispatch: interfaces