User Interface Development

Submit your proposals for Interop 2027

The annual initiative to harmonize the web platform, known as Interop, has officially entered its planning phase for 2027. As of September 3, 2026, the project organizers have opened the public submission period, inviting developers, engineers, and stakeholders to nominate specific web features for inclusion in next year’s interoperability roadmap. This critical window, which remains open until September 23, marks the beginning of a multi-month vetting process designed to identify the most pressing cross-browser compatibility challenges facing the modern web ecosystem.

The Interop project represents a collaborative effort between major browser engine vendors—including Chromium (Google, Microsoft, Samsung), Gecko (Mozilla), and WebKit (Apple)—to address the long-standing issue of fragmented feature support. By prioritizing specific web technologies, the project seeks to ensure that features function consistently across all browsers, thereby reducing the "works on my machine" phenomenon that has plagued web development for decades.

A Proven Framework for Collaborative Improvement

The success of previous iterations, such as Interop 2024, 2025, and the ongoing 2026 cycle, has fundamentally changed how browser vendors coordinate their development efforts. The methodology relies on a data-driven approach to selection. Rather than choosing features based on popularity alone, the selection committee mandates that nominated features possess a stable specification. This requirement ensures that the underlying technology is mature enough for implementation without requiring significant design changes during the testing phase.

Furthermore, a critical prerequisite for any successful proposal is the existence—or the capacity to create—a robust suite of tests. The project’s progress is tracked via the Web Platform Tests (WPT) dashboard, an industry-standard repository that serves as the "source of truth" for compliance. Without a comprehensive test suite, it is impossible for engineers to verify that a feature has achieved true interoperability, as subjective interpretations of specifications often lead to subtle differences in behavior across different engines.

The Evolution of the Selection Process

The timeline for Interop 2027 follows the established rhythm of previous years. Following the September 23 deadline for submissions, the proposal period closes. The subsequent phase involves an exhaustive review where proponents must demonstrate clear use cases and evidence of demand. The process is governed by a public repository, ensuring transparency throughout the decision-making lifecycle.

Historically, the project has leaned on "developer signals" to gauge the pain points of the community. In 2026, many of the selected features were identified through major industry surveys, such as the State of CSS, and through the developer signals repository hosted by the Web Platform Developers Group. By synthesizing survey data with technical feasibility, the Interop committee has been able to bridge the gap between user needs and engineering realities.

Submit your proposals for Interop 2027  |  Blog  |  web.dev

Current Landscape: Assessing Interop 2026

As the industry looks toward 2027, the progress of the 2026 project serves as both a benchmark and a testament to the initiative’s efficacy. Mid-year reporting indicates that browsers are currently in their strongest position to date regarding the attainment of full compatibility across the 2026 feature set.

Data from the Interop 2026 dashboard reveals high scores across major engines. As of early September, Chromium-based browsers (Chrome and Edge) have consistently led the pack, with Safari and Firefox showing significant closing of the gap in previously problematic areas like subgrid, typography, and complex layout properties. The shift is palpable; in years past, it was not uncommon for a feature to be "implemented" in one browser while remaining entirely non-functional in another for years. Today, the lag between feature proposal, implementation, and cross-browser stability has been compressed significantly.

Strategic Implications for the Web Ecosystem

The implications of the Interop project extend far beyond mere browser testing. For businesses and individual developers, the initiative provides a degree of predictability that is essential for long-term project planning. When a feature is marked for the Interop project, developers can be reasonably confident that it will be supported universally within the near future, allowing them to adopt newer web standards without the burden of maintaining extensive polyfills or "fallback" code for different browsers.

This reduction in technical debt has profound economic benefits. Maintenance costs for web applications are often driven by the need to debug cross-browser quirks. By standardizing the behavior of CSS properties, DOM APIs, and JavaScript features, the Interop project effectively lowers the barrier to entry for high-performance, cross-platform web applications.

How to Influence the 2027 Roadmap

The organizers have emphasized that the success of Interop 2027 relies heavily on community participation. For those wishing to contribute, the process is not limited to those who have the capacity to write code or submit formal proposals. The project’s public repository on GitHub allows any member of the developer community to comment on, react to, or "like" existing proposals. These community interactions serve as a proxy for developer sentiment and are actively considered by the committee when prioritizing the final list of features.

Engineers and researchers are encouraged to utilize resources such as webstatus.dev to verify the current state of proposed features. This tool provides a granular look at the implementation status of various web standards across different engine versions. By cross-referencing these status updates with the developer signals repository, proponents can build a compelling case that a feature is both technically ready and high-priority for the developer community.

The Role of Stakeholder Consensus

One of the most challenging aspects of the Interop project is reaching a consensus among browser vendors who, while committed to the open web, often have competing priorities regarding their own development roadmaps. The Interop process forces these vendors to sit at the same table and negotiate the prioritization of specific standards.

Submit your proposals for Interop 2027  |  Blog  |  web.dev

This cooperative model has, in effect, created a "de facto" priority list for the web. When a feature is added to the Interop list, it effectively moves to the top of the engineering queue for browser vendors. This alignment of resources is perhaps the most significant achievement of the initiative. By focusing the combined efforts of industry giants on a specific set of 10 to 20 features annually, the project ensures that the web platform evolves in a cohesive, rather than fractured, manner.

Looking Ahead: Anticipated Focus Areas

While the final list for 2027 remains to be determined, several recurring themes are expected to dominate the discussion. Accessibility, performance APIs, and advanced layout capabilities—particularly those related to container queries and viewport units—have consistently been high on the list of developer requests. As the web continues to compete with native application environments, the need for robust, high-performance APIs becomes increasingly critical.

Furthermore, as privacy and security standards evolve, the Interop project is likely to see an increase in proposals related to privacy-preserving technologies and secure communication APIs. Balancing the need for powerful web capabilities with the imperative of user security is a central tension that the standards bodies and the Interop project will need to navigate in the coming years.

Conclusion

The opening of the Interop 2027 call for proposals is a reminder that the web is a living, breathing entity that requires active maintenance and collaboration to remain viable. The transition from a fragmented collection of browser behaviors to a unified, predictable platform is the ultimate goal of the Interop project.

Whether you are a developer struggling with a specific CSS quirk, a lead engineer tracking feature support for a large-scale project, or a hobbyist interested in the evolution of web standards, the current proposal period offers a rare opportunity to have a direct impact on the future of the internet. By participating in the selection process, the community ensures that the web remains the most powerful and accessible platform for information and application delivery in the world. As the industry moves through the remainder of 2026, all eyes will be on the incoming proposals and the subsequent selection process that will define the web of 2027.

Related Articles

Back to top button
Whatvis
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.