Browser Interoperability Initiative Opens Community Proposal Window for Interop 2027

Key facts

On September 7, 2026, Patrick Brosset issued a public call for proposals on behalf of the Interop project team, initiating the community input phase for the Interop 2027 planning cycle. The announcement marks the beginning of an open submission period during which web developers, software engineers, and digital design practitioners can submit formal proposals detailing web features that exhibit buggy, incomplete, or divergent behavior across different web browsers.

To be eligible for inclusion in the Interop 2027 program, submitted proposals must focus on web platform features that are already formally standardized or nearing final specification by recognized web standards organizations, such as the World Wide Web Consortium (W3C) or the Web Hypertext Application Technology Working Group (WHATWG). The project specifically excludes proposals for unstandardized, proprietary, or brand-new feature ideas, concentrating entirely on resolving existing interoperability gaps within established specifications.

Once the public proposal window concludes, submissions will undergo a structured evaluation process led by the Interop steering group, which includes engineers and community coordinators from major browser vendors and web consulting organizations. The review panel will assess candidate proposals based on the severity of developer pain caused by engine discrepancies, the current availability and quality of automated tests in the Web Platform Tests repository, and the willingness of vendor engineering teams to commit resources toward fixing identified defects during 2027. Selected proposals will ultimately form the official focus areas for Interop 2027, complete with automated metric tracking dashboards.

Why it matters

The opening of the Interop 2027 proposal window represents a vital structural mechanism for reducing friction across the digital software economy. For millions of web developers and software engineering teams globally, inconsistencies between browser engines—primarily Apple WebKit, Google Blink, and Mozilla Gecko—create persistent operational challenges. When browsers interpret CSS rules, execute JavaScript APIs, or render graphical interfaces differently, developers are forced to write complex workaround scripts, maintain fragile feature detection logic, or perform exhaustive multi-browser testing routines.

These technical discrepancies directly translate into inflated software development costs, delayed product release schedules, and degraded end-user experiences across different devices and operating systems. By establishing a shared, objective benchmark agreed upon by competing browser vendors, the Interop program aligns engineering priorities across corporate boundaries. When browser manufacturers focus on a common set of interoperability goals, long-standing bugs and missing platform capabilities are systematically resolved.

Furthermore, the Interop methodology transforms browser engine development from an opaque, internal corporate process into a transparent, data-driven public effort. By tracking test pass rates on publicly accessible scorecards, the project holds browser maintainers accountable to the broader developer ecosystem. This collaborative benchmarking framework ensures that modern web capabilities—ranging from sophisticated page layout modules to advanced application programming interfaces—can be deployed universally without requiring browser-specific hacks or platform-exclusive fallback code.

The challenge of web interoperability dates back to the earliest decades of the commercial internet, widely characterized by the initial browser wars of the late 1990s and early 2000s. During that era, competing browser vendors routinely introduced proprietary HTML tags, non-standard JavaScript extensions, and incompatible document object models in an attempt to capture user market share. This fragmentation created severe burdens for web creators and highlighted the necessity of rigorous, open specifications.

While standard-setting bodies such as the W3C and WHATWG succeeded in drafting open specifications for core web technologies, written standards alone proved insufficient to guarantee identical behavior. Software codebases built on different rendering architectures—such as WebKit, Blink, and Gecko—frequently interpreted ambiguous specification language differently, leading to subtle cross-browser inconsistencies even when all engines claimed adherence to the same standard.

To address these implementation gaps, browser vendors and industry partners established structured, collaborative alignment efforts. In 2021, major industry stakeholders launched Compat2021, a targeted initiative aimed at resolving high-priority CSS rendering issues across major engines. The success of Compat2021 demonstrated that vendor collaboration backed by shared automated testing could dramatically accelerate bug remediation.

Building upon that foundation, the initiative expanded into the formal Interop program, launching Interop 2022, followed by annual iterations including Interop 2023, Interop 2024, Interop 2025, and Interop 2026. Participating entities—including Apple, Google, Microsoft, Mozilla, Bocoup, and Igalia—agreed to jointly select critical web technologies each year and measure cross-engine compliance using the Web Platform Tests project. Over successive years, Interop has successfully driven cross-browser parity across major web platform capabilities, including CSS container queries, flexbox and grid layouts, popover APIs, color spaces, dialog elements, and custom properties.

Reaction

The launch of the Interop 2027 proposal call has drawn engagement from web developers, open-source maintainers, and platform engineers who rely on standardized web technologies. Within developer forums and social media channels, practitioners regularly highlight persistent pain points in modern web development, such as inconsistencies in custom element lifecycles, advanced typography rendering, media stream handling, and form control styling.

Engineers and standards representatives from Apple, Google, Microsoft, and Mozilla are expected to participate actively in reviewing public proposals as they are logged in the project's central repository. Technical leads from consulting firms such as Igalia and Bocoup, who frequently contribute core engineering work to open-source rendering engines, will also review candidates to evaluate test suite completeness and implementation feasibility.

Members of W3C working groups and WHATWG workstreams are monitoring the proposal submissions closely. For standards authors, candidate proposals that generate high developer interest often reveal underlying ambiguities or edge cases in written specification text, providing valuable signals regarding which specification documents require editorial clarification or additional normative test cases.

What we don't know yet

Several key details regarding the Interop 2027 cycle remain undetermined at this early stage of the process:

What to watch

Key milestones and developments to monitor throughout the Interop 2027 selection and execution phases include:

This report is based on original reporting published by patrickbrosset.com.