The annual initiative to harmonize the web platform, known as Interop, has officially entered its planning phase for the 2027 cycle. As of September 3, 2026, the project organizers have opened the public submission window, inviting developers, engineers, and stakeholders to nominate specific web platform features for inclusion in the upcoming year’s cross-browser compatibility efforts. This announcement marks a critical juncture in the ongoing multi-year mission to reduce fragmentation across major browser engines, including Chromium, WebKit, and Gecko.
The Foundation of the Interop Project
The Interop project was conceived as a collaborative endeavor between browser vendors and the wider web community to address one of the most persistent challenges in software development: the inconsistency of feature implementation across different browsers. For years, developers have struggled with the "works in Chrome but not in Safari" dilemma, a problem that necessitates excessive polyfills and defensive coding practices. By selecting a set of focus areas—typically new CSS modules, JavaScript APIs, or HTML elements—the project mandates that participating browser vendors dedicate engineering resources to ensure these features reach parity in functionality and testing.
The selection process for Interop 2027 is highly structured to ensure that only viable, high-impact features are chosen. The proposal period, which remains open until September 23, 2026, requires that potential candidates have already moved past the experimental phase. Specifically, the Interop steering committee seeks features with stable specifications, lacking significant opposition from any major browser vendor, and supported by a robust existing test suite.
Historical Context and Evolution
The inception of the Interop project—initially launched as Interop 2022—represented a paradigm shift in how the web is governed. Before this initiative, browser vendors often prioritized proprietary feature roadmaps. The collaborative nature of the Interop initiative forces a collective focus on the "Web Platform Tests" (WPT) repository, which acts as the definitive source of truth for browser compliance.
By 2024 and 2025, the project had matured significantly, shifting from tackling fundamental layout issues to addressing more nuanced developer experience (DX) concerns. The data from the 2026 cycle indicates that this strategy is paying off. According to current dashboard metrics, the collective performance of browsers has reached unprecedented levels of consistency, with major vendors consistently hitting high scores in compliance testing. This year, the focus has shifted toward refining the selection process to better align with the actual pain points reported by the global developer community.
Analyzing the Selection Criteria
What separates a successful proposal from one that is dismissed? The selection committee, which includes representatives from Google, Apple, Microsoft, Mozilla, and others, looks for three specific markers of success:
- Specification Stability: The feature must be beyond the draft stage. A feature in flux is difficult to test and implement consistently.
- Existing Implementations: The project is not meant to be a laboratory for cutting-edge, untested technologies. Rather, it is designed to finalize and polish features that have already been deployed in at least one browser environment.
- Test Suite Readiness: A proposal is only as good as the tests backing it. If a feature lacks a comprehensive suite of Web Platform Tests, it cannot be effectively measured. Participants are encouraged to use the
webstatus.devportal to audit the technical readiness of their suggested features.
Leveraging Developer Signals
A significant enhancement in the 2027 process is the formalized integration of "developer signals." In previous years, the selection was often driven by internal browser metrics or isolated engineering feedback. Now, the project relies heavily on data-driven insights from platforms such as The State of CSS survey and the developer signals repository on GitHub.
These signals serve as a proxy for market demand. When a feature receives widespread support in developer polls, it creates a mandate for browser vendors to prioritize it. This shift ensures that the Interop project remains democratic, preventing a scenario where engineering convenience overrides user needs. Developers are encouraged to document their use cases—explaining exactly why a particular feature is causing friction in their current workflow—within the proposal threads to bolster their submissions.
The State of Interop 2026: A Progress Report
As of early September 2026, the performance metrics for Interop 2026 demonstrate a strong trajectory. Browser engines that historically lagged in specific CSS or API support have closed the gap significantly. The dashboard on wpt.fyi/interop-2026 provides a transparent view of this progress, showcasing the scores for major engines. At this stage in the year, most browsers have crossed the 90% threshold for their target features, a stark improvement compared to the same period in 2025.
The implication of these gains is substantial for the broader web ecosystem. Reduced fragmentation means that developers can write cleaner code, rely less on transpilers like Babel, and spend less time debugging browser-specific quirks. This, in turn, lowers the barrier to entry for new web developers and increases the overall performance of the web as a platform compared to native mobile applications.
Engaging the Community
The success of Interop 2027 depends on broad participation. The organizers have emphasized that the call for proposals is not limited to large corporate entities or core browser engine contributors. Individual developers and small open-source maintainers are encouraged to weigh in on the list of proposals. Even if a user does not submit a formal proposal, the act of "liking" or commenting on existing proposals on GitHub helps the committee gauge the community’s priority levels.
Furthermore, the transparency of this process is a cornerstone of the project’s longevity. By keeping the discussion in public forums, the community can track the evolution of the web platform in real-time. This open-source approach to web standards has effectively mitigated the "walled garden" approach that defined the browser wars of previous decades.
Broader Implications and Future Outlook
Looking ahead, the Interop 2027 initiative is expected to address the next frontier of web development: performance, security, and advanced interactivity. As web applications grow more complex—approaching the capability of desktop software—the need for consistent implementation of features like WebAssembly, advanced storage APIs, and complex rendering techniques becomes critical.
The timeline for the coming months is clear:
- September 3, 2026: Call for proposals opens.
- September 23, 2026: Deadline for all proposals.
- October–November 2026: Review and selection process by the technical steering committee.
- Early 2027: Official announcement of the selected focus areas for Interop 2027.
The Interop project stands as a testament to the fact that the web is not a static technology but a living, evolving ecosystem that thrives on cooperation. By soliciting input from the very people who build the web, the project ensures that the standards of tomorrow reflect the realities of today. As the September 23 deadline approaches, the web community’s participation will determine which features define the capabilities of the browser landscape for the remainder of the decade. For those looking to shape the future of the web, the call for proposals is the most direct mechanism to effect change at the engine level.
