Interop 2026 Makes Anchor Positioning Work Everywhere

Interop 2026, the yearly pact where every major browser maker commits to passing the same web-platform test suites, has delivered its biggest practical win yet: CSS anchor positioning now works the same across Chrome, Firefox, Safari and Edge, alongside baseline support for View Transitions, the Popover API and WebGPU. In plain terms, features that used to require JavaScript libraries and per-browser hacks are now native and interoperable, which is the quiet, unglamorous work that actually makes the web easier to build on. This is what progress looks like when it is measured in shared tests rather than press events.

• Interop 2026 is run jointly by Apple, Google, Microsoft, Mozilla, plus Igalia and Bocoup, picking features each year and holding all engines to the same tests.
• This cycle shipped baseline cross-browser support for anchor positioning, View Transitions, the Popover API and WebGPU.
• Anchor positioning lets the browser tether a tooltip or menu to an element and reposition it automatically, replacing libraries like Popper.js and Floating UI.
• The gap between the top browser engines on standards compliance has narrowed to about 2 points, down from 6 a year earlier.

What is Interop and why does it exist?

Interop is a joint project among the browser makers, Apple, Google, Microsoft and Mozilla, with consultancies Igalia and Bocoup, to fix the web's oldest complaint: the same code behaving differently in different browsers. Each year the group selects a set of platform features and commits every engine to passing the identical Web Platform Test suites for them. Instead of one vendor shipping a feature and everyone else catching up on their own timeline, all engines aim at the same measurable target in the same cycle. Progress is public and numeric, tracked on dashboards, which is why Interop has become the most reliable engine of cross-browser consistency the web has.

RelatedWebMCP Lets Websites Talk Directly to AI Agents

Why is anchor positioning the standout win?

Because it kills a whole category of workaround. Positioning a tooltip, dropdown or popover so it stays attached to its trigger and flips when it hits the viewport edge sounds trivial, but for years it required JavaScript libraries like Popper.js or Floating UI, each with its own bundle size, quirks and edge cases. CSS anchor positioning lets you declare that relationship in CSS and hands the repositioning math to the browser, which recomputes as the element scrolls or the layout changes. Getting it interoperable across all four engines means front-end teams can delete a dependency and trust the platform to do the work, faster, lighter, and with no library to keep updated.

What do View Transitions and WebGPU add?

They round out a platform that increasingly does natively what used to need frameworks. View Transitions let the browser animate between two page or DOM states, smooth crossfades and shared-element moves, without the hand-rolled animation code that single-page apps leaned on, and now it behaves consistently everywhere. The Popover API gives menus, dialogs and tooltips built-in show and hide, focus and accessibility behavior, again replacing bespoke JavaScript. WebGPU is the heavyweight: direct GPU access from the browser for compute and rendering, enabling in-browser AI inference, console-quality games and GPU-accelerated visualization, now supported by roughly 82% of browsers. Together they shift real capability from libraries into the platform itself.

Does this actually close the browser gap?

On standards, yes, and measurably. Testing this year shows the total-score spread between the top three engines has shrunk to about 2 points, down from 6 a year earlier, so focused, shared targets are visibly converging the implementations. Chrome still leads, with Edge and Safari close behind and Firefox further back, but the practical experience for developers is that the features Interop covers can now be used without defensive per-browser code. That said, Interop only moves what it selects: features outside a given year's list still ship at each vendor's pace, and rendering-engine diversity remains thin, with most browsers built on Chromium. Interop narrows behavior gaps; it does not fix the deeper concentration of the engine market.

RelatedLadybird Is Building the First New Browser Engine in Years

Our take

Interop is the least flashy and most valuable thing happening on the web, and this cycle proves why. Making anchor positioning, View Transitions, the Popover API and WebGPU behave identically across engines does not trend, but it removes friction from millions of hours of front-end work and lets developers delete dependencies they only carried because browsers disagreed. The 2-point compliance gap is a genuine achievement earned by shared tests rather than marketing. The honest caveat is that Interop treats symptoms, behavior fragmentation, not the underlying condition, an engine market dominated by Chromium, so a healthier web still needs independent engines to keep the incumbents honest. But for the everyday job of building sites that just work everywhere, Interop 2026 is the best news of the year, and it is the kind of progress worth celebrating precisely because nobody staged an event for it.

Original analysis by GenZTech. Figures current as of July 2026. Source: wpt.fyi