Skip to main content
FreeAn audit of your Drupal siteA written audit of your Drupal site, within three business days
All articles

PerformanceOct 30, 20264 min read

The browser got better in 2026, and your website benefits

Eric ZsigmondCo-Founder & Senior Frontend Engineer

Something quietly good happened to the web in 2026. Features that front-end developers had wanted for a decade, and had been simulating with layers of JavaScript, became available in every major browser at the same time. Smooth transitions between pages. Popups and dialogs that just work. Layouts that respond to the size of their container rather than the whole screen. Animations tied to scrolling. These are now part of the platform, and a site built on web standards gets them for free. This article is about what changed, why it matters to a business, and why we build on the browser rather than around it.

The browsers agreed

The reason this happened is a project called Interop, in which the makers of Chrome, Safari, Firefox and Edge agree each year on a list of features to implement consistently, and then do. The 2026 list included view transitions, popovers and dialogs, container queries, scroll-driven animations, anchor positioning, the Navigation API and a set of CSS functions that make layouts and colors adapt automatically. The related Baseline effort tracks when a feature is safe to use everywhere, and this year the "safe" list grew faster than in any previous year.

For most of the web's history, using a new browser feature meant waiting years for the slowest browser or shipping a fallback for it. In 2026, the wait shrank to months, and for a growing set of features to nothing at all.

What it means for your site

The practical effects are the ones visitors notice without knowing why.

Pages that flow into each other. View transitions let a click on a product card animate smoothly into the product page, with the image moving into place rather than the screen flashing white. This used to require a single-page application and a great deal of code. Now it is a few lines of CSS on a normal, server-rendered Drupal page, and it makes a site feel considerably more polished.

Dialogs and menus that behave. The popover and dialog features handle focus, keyboard dismissal, stacking and accessibility announcements natively. A dropdown or a modal built on them is smaller, faster and more accessible than one built by hand, and it works the same way in every browser.

Components that fit where they are placed. Container queries let a card lay itself out differently depending on whether it sits in a sidebar or a full-width grid, without the page telling it. That is exactly the property a component library needs: build the card once, place it anywhere, and it adapts.

Less JavaScript. Every one of these features replaces code that used to ship to the visitor's browser. Less code means faster pages, fewer things to break and fewer dependencies to keep current. Performance improves as a side effect of using the platform.

Why we build on standards

There is a choice in how to build a modern interface. One path is to adopt whatever framework is most popular this year and let it provide the features, accepting that the framework will change and eventually be replaced. The other is to build on the browser's own capabilities and use a framework only for what the browser does not yet do. We take the second path, and 2026 is a good illustration of why.

Features that are part of the web platform do not go away. They do not have breaking releases. They are maintained by the browser makers, tested against billions of pages, and optimized at a level no library can match. A component built on a native dialog in 2026 will still work, unchanged, in 2036. A component built on a library's dialog will have been rewritten twice by then. Our React components render on the server and use the browser's features for behavior wherever they exist, so the framework does the composition and the platform does the work.

Progressive enhancement, still

Not every visitor has the newest browser, and a site that only works on the latest version excludes the people it most needs to include. So we build in layers: the page works completely with HTML and CSS alone, works better with the new features where the browser supports them, and works best with the interactive components on top. A visitor on an older device gets a fast, usable site. A visitor on a current one gets the transitions and the polish. Nobody gets a blank page. This is an old principle, and the 2026 features fit it well because most of them enhance rather than replace: a view transition that is unsupported simply becomes an ordinary page load.

What this means for how a site ages

The sites that age well are the ones built close to the platform. Their code is smaller, their dependencies fewer, and every year the browsers make them a little better without anyone touching them. That is the position we want every client's site to be in: benefiting from the web's improvement rather than being stranded by it. It is also why some sites cost less to change: there is less to change, and what exists is built on ground that holds still.

If your site was built a few years ago and feels heavier than it should, a good portion of that weight is likely doing work the browser now does for free. We are happy to look at what could be simplified, and what your visitors would notice if it were.

Written by

Eric Zsigmond

Co-Founder & Senior Frontend Engineer

Frontend engineer with deep expertise in Drupal theming, component-driven architecture, and modern JavaScript frameworks. Builds fast, accessible interfaces using React, SDX, and Tailwind. Obsessive about performance, pixel-perfect implementation, and clean markup. Almost every pixel on this page is his work.

Enjoyed this article?

If this resonated, imagine what we could do working together on your Drupal site.