Skip to content
Technical notes15 Nov 2026

Most of what a web page needed script for is now HTML

Felix Hellström

Felix Hellström

Founder, Klarhimmel

A white browser window with page sections on a pale blue stand, beside a navy set square and a pencil.

Every website we build is made from a library of parts: a hero, a price list, a menu, a booking form. Today those parts are React components. Before we decide what format they should have next, I asked the agents to read what the browsers themselves have shipped, straight from the source. On 14 November four of them read a year of release notes for Chrome, Firefox and Safari, up to Chrome 158, Firefox 160 and Safari 27.2, with the betas after them, and the year's summaries on web.dev and from the committee that writes JavaScript.

The short version: a lot of what a page used to need JavaScript for, the browser now does by itself, in all three engines.

What works everywhere now

A button can open a dialog or a popover without a line of script. You give it commandfor and the name of what it opens, and the browser handles opening, closing, focus and the Esc key. Accordions where only one section is open at a time are a <details> element with a shared name. Menus and tooltips can be placed next to the button that opened them with anchor positioning, which used to be the main reason to load a positioning library.

Styling has caught up in the same way. Container queries can react to a component's own settings, not only its width, so a dark variant of a section can be one attribute. @scope keeps a part's styles inside that part without a shadow root. contrast-color() picks readable text for any background, which matters when an agent picks the colours. Scroll-driven animations, field-sizing for text boxes that grow as you type, and text-box-trim for even spacing around headings all reached every engine this year.

Web Components lost their two old objections. Scoped custom element registries reached all three browsers on 27 October, when Firefox 159 shipped them, so two libraries can each define an element with the same name without colliding. And styles that work in the normal page, with @scope, mean a component doesn't have to hide inside a shadow root to keep its look.

What doesn't, yet

Some of the most useful features are in two engines out of three. Typed attr(), where a part's attributes set its size or colour directly in CSS, is in Chrome and Firefox, and in Safari's 27.3 beta. setHTML(), which inserts HTML with anything unsafe stripped out, is in Chrome and Firefox. A fully styleable <select> is in Chrome and Safari, with Firefox still behind a setting.

Others are Chrome only among released browsers: CSS if() and @function (both in Safari's 27.3 beta), arrow-key navigation declared in markup, streaming parts of a page out of order. We treat those as previews, not something a customer's page can depend on.

In JavaScript, this year's finished additions are small conveniences: chaining iterators, exact sums, Base64 on byte arrays, Array.fromAsync. Temporal, a proper date and time API, is in Chrome and Firefox and in Safari's preview. Once Safari ships it, it suits anything that stores opening hours and dates.

For agents

Two changes are aimed at agents directly. WebMCP lets a page offer tools to an AI agent, either declared on a form or written in script. It is an origin trial in Chrome since 149, Edge runs its own, and Firefox and Safari have nothing yet. It is the browser version of the idea behind our own front desk for agents, which works today in any MCP client without waiting for browsers.

Safari 27 ships an MCP server of its own, safaridriver --mcp, which gives a coding agent the page's structure, network requests, screenshots and console. That is the kind of access our agents use to walk a page as a visitor would before they call it done.

What it changes for us

The behaviour in our parts shrinks. Disclosure, accordion, dialog, menu and tooltip need no script in any engine. What still needs code is a short list: tabs, a searchable dropdown, drag and drop.

The look shrinks too. With style container queries and @scope, a variant of a part is an attribute, and a part is HTML and CSS.

So the source an agent writes for a page can be close to plain HTML: elements, the platform's own attributes for behaviour, our design tokens as classes, and a few places where content is filled in. React, static HTML and Web Components become outputs of that source, not the thing the agent has to get right. A part shipped as <kh-hero-centered> works in a static page, in React 19 and in anything else.

We haven't picked the format yet. We are measuring it: fresh agents build the same pages from three candidate formats, and the one they get right most often wins. This reading tells each format what it is allowed to assume.

If you build pages yourself

Before you add a library for a dropdown, a modal or a tooltip, check whether the browser already does it. Most of the time, in November 2026, it does. Check the support table for the one feature you need rather than a general impression, and keep anything that is in one engine only behind a fallback.

Our sources are the release notes themselves, read on 14 November 2026. A feature that wasn't named in a changelog we read is unconfirmed, not absent, and where two sources gave different versions we used the range.

Start with a page for your business

Describe your business or paste your website, and a first page builds while you watch. Free, no card, no sign-in.