What Interop 2026 Commits the Browser Vendors To

Interop 2026 is now official. Blink (Chrome and Edge), WebKit (Safari), and Mozilla (Firefox) have agreed to pursue full, consistent support for a shared set of CSS features — many of which have until now required a "lack of browser support" caveat. The vendors published their own announcements: web.dev, the WebKit blog, Mozilla Hacks, and the Edge blog.

For CSS specifically, the slate is substantial.

Newer CSS Features on the List

Tracking one element against another

Anchor positioning lets an element be attached to another by declaring which sides connect, entirely in CSS, with a fallback position available to guard against overflow.

Typed attr()

The attr() function has existed for roughly 15 years, but Interop 2026 covers passing variables into it with type conversion:

.element { color: attr(data-color type(<color>)); }

Styling from styles

Containers can already be queried by size. Style queries extend that so styles can be applied based on other styles — see the example below.

@container style((font-style: italic) and (--color-mode: light)) {
  em, i, q {
    background: lightpink;
  }
}

contrast-color()

Picking a readable foreground against a background has largely been a manual job, sometimes switched with a media query tied to the color scheme. contrast-color() toggles color between white and black dynamically. (It was originally named color-contrast().)

button {
  --background-color: darkblue;
  background-color: var(--background-color);
  color: contrast-color(var(--background-color));
}

Highlighting arbitrary ranges

::selection has long been the only highlight in town; the Custom Highlight API and related pseudo-elements add many more.

Pseudo-selectorSelects…Notes
::search-textFind-in-page matches::search-text:currentselects the current target
::target-textText fragmentsText fragments allow for programmatic highlighting using URL parameters. If you’re referred to a website by a search engine, it might use text fragments, which is why ::target-text is easily confused with ::search-text.
::selectionText highlighted using the pointer
::highlight()Custom highlights as defined by JavaScript’s Custom Highlight API
::spelling-errorIncorrectly spelled wordsPretty much applies to editable content only
::grammar-errorIncorrect grammarPretty much applies to editable content only

Media element states

Instead of reaching for JavaScript, styles can key off the playback state of <audio> and <video> elements via the following pseudo-classes:

  • :playing
  • :paused
  • :seeking
  • :buffering
  • :stalled
  • :muted
  • :volume-locked

The WebKit announcement offers a good demonstration:

video:buffering::after {
  content: "Loading...";
}

Complex shapes for clip-path

circle, ellipse(), and polygon() have covered basic shapes for years, but drawing something more complex meant going SVG-ish. shape(), used with clip-path, accepts CSS units and calculations instead.

.clipped {
  width: 250px;
  height: 100px;
  box-sizing: border-box;
  background-color: blue;
  clip-path: shape(
    from top left,
    hline to 100%,
    vline to 100%,
    curve to 0% 100% with 50% 0%,
  );
}

zoom, at last standard

This one comes as a surprise: zoom has shipped for years as a non-standard property. It reached Baseline 2024 as newly available, was worked on through Interop 2025, and carries over into 2026. Unlike scale(), which is purely visual and paints over whatever sits in its path, zoom affects layout.

Features Moving Toward Consistent Cross-Browser Behavior

Declarative top-layer content

Dialogs and popovers give a JavaScript-free, declarative route to placing elements on the top layer. The details worth knowing include how popovers and dialogs relate to each other, and that a <dialog> element does not require focus trapping.

Animation tied to scroll position

Scroll-driven animations link an animation's progress directly to scrolling progress. Supporting APIs include view():

.element { animation-timeline: view(); }
#progress {
  animation: grow-progress linear forwards;
  animation-timeline: scroll();
}

Page-to-page transitions

View transitions come in two forms: same-document transitions on a single page, which reached Baseline in 2025, and cross-document (multi-page) transitions, for which browsers are now working toward cross-compatible implementations. Related pieces include the types descriptor, the ::view-transition family of pseudo-elements, the @view-transition at-rule:

@view-transition { navigation: auto; }

and properties such as view-transition-name:

.element { view-transition-name: image-zoom; }

Scroll snapping: catching up to the spec

Nothing new in concept here — the goal is bringing implementations in line with how the specifications have evolved. The relevant properties:

.scroll-element { scroll-margin: 50px 0 0 50px; }
.scroll-element{ scroll-padding: 50px 0 0 50px; }
.element { scroll-snap-align: start; }
.element { scroll-snap-stop: always; }
.scroll-element { scroll-snap-type: y mandatory; }

Where to Follow Progress

Track implementation status across all engines on the Interop 2026 Dashboard.