Baseline 2026: the APIs that finally replace old libraries

The Navigation API became Baseline Newly available in early 2026 (Chrome, Edge, Firefox 147, Safari 26.2). It replaces the brittle History API ritual — pushState one way, popstate another, manual scroll restoration — with a coherent model for same-document navigations.

You will not delete React Router or your framework’s file router tomorrow. You should stop assuming client-side routing requires a heavyweight library for every marketing site and content app. For many products the platform is now enough, and the bundle you do not ship is the one that never blocks Interaction to Next Paint.

Container style queries for custom properties became Baseline Newly available in May 2026 once Firefox 151 closed the gap. Components can respond to a parent’s custom properties without threading theme props through three layers of React. The :open pseudo-class and field-sizing reached the same Baseline status around May–June, covering disclosure widgets and auto-growing form fields that used to mean a small script.

Interop 2026 is still grinding on consistency for things like anchor positioning. Baseline Newly available is not the same as Widely available (30 months of interoperability). Feature-detect, provide a fallback, and prefer the platform when the support matrix says yes.

Agent demos get the clicks. Platform baselines get the durable traffic. Search demand for “can I use Navigation API”, container style queries, and Baseline 2026 is the kind of query stream a studio site can own for months — and it maps directly to how we build peeklink, saveio and client sites: less JavaScript where the browser already solved the problem.

If you are rewriting a marketing site or a docs shell this quarter, audit the dependency list against Baseline. Every library you delete is one less hydration cost and one less supply-chain surface — a quieter win than a kill switch bill, and one you can ship this week.

On new FuriaHub and client work we default to platform features first, framework features second, and npm packages third. That order used to be aspirational. With Navigation API and container style queries on Baseline, it is operational.

We still use React and Next.js where the product needs them. We stop pretending every interactive detail needs a client component. The browser earned another shift of the work; take it.