Chromium's Role in the Annual Interop Benchmark Initiative

This article provides a comprehensive overview of the vital role the Chromium team plays in the annual Interop benchmark initiative alongside Apple, Mozilla, and Microsoft. It covers how Chromium engineers collaborate with rival browser vendors to select priority web features, author cross-browser tests, and update the Blink rendering engine to eliminate compatibility bugs and create a unified, predictable web platform for developers.

The Interop initiative is a cross-browser effort aimed at making the web work consistently across all major browsers. In this partnership, Apple represents the WebKit engine (Safari), Mozilla represents the Gecko engine (Firefox), and the Chromium team—primarily led by Google in tandem with Microsoft—represents the Blink rendering engine. Because Chromium is the open-source foundation for Google Chrome, Microsoft Edge, Brave, Opera, and Vivaldi, the Chromium team's contributions impact the vast majority of global internet traffic.

Selecting Annual Focus Areas

Before a new yearly Interop benchmark is launched, the Chromium team works directly with Apple, Mozilla, and web standards consultancies like Bocoup and Igalia to decide which technologies to target. The Chromium team’s responsibilities during this phase include:

  • Analyzing Developer Pain Points: Reviewing data from community surveys, such as the State of CSS and State of HTML reports, to identify which browser inconsistencies frustrate web developers the most.
  • Evaluating Proposals: Reviewing public feature proposals submitted by developers and industry stakeholders.
  • Consensus Building: Negotiating with other browser vendors to finalize a list of 15 to 25 specific focus areas—such as CSS Grid, Subgrid, Flexbox, or Pointer Events—that all teams agree to prioritize for the year.

Authoring Web Platform Tests (WPT)

The Interop benchmark is measured entirely through the Web Platform Tests (WPT) project, a massive suite of automated tests used to verify if browsers follow official W3C and WHATWG specifications. The Chromium team plays a massive role in maintaining this grading system.

Chromium engineers write new tests for the selected Interop focus areas and audit existing tests to ensure they are fair and accurate. If a test is flawed, the Chromium team collaborates with Mozilla and Apple engineers to fix the test logic rather than altering the browser to pass a broken test.

Fixing Bugs and Implementing Features

Once the annual Interop dashboard goes live, each browser is given a score from 0 to 100 based on how many tests it passes. To push Chromium’s score toward 100, the team focuses on updating the Blink rendering engine and the V8 JavaScript engine. Their engineering efforts include:

  • Triaging Failures: Identifying why Chromium fails specific Interop tests and assigning those bugs to specialized engineering teams.
  • Rewriting Legacy Code: Updating older parts of the Chromium codebase—such as table rendering or form controls—to match modern web specifications.
  • Shipping New Standards: Writing the code for brand-new CSS, HTML, and JavaScript features so they launch simultaneously with Safari and Firefox, preventing future compatibility gaps.

Collaborating with Microsoft

Within the Interop initiative, Google and Microsoft share a unique relationship because Microsoft Edge is built on the Chromium open-source project. Rather than duplicating work, Google’s Chromium engineers and Microsoft’s Edge engineers divide the labor. For example, Microsoft might take the lead on fixing Chromium's accessibility or CSS Grid bugs for the Interop benchmark, while Google focuses on Color Spaces and Typography. Once either company merges the code into the Chromium project, the Interop scores for both Chrome and Edge rise simultaneously.