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 floor for public submissions, inviting developers, engineers, and stakeholders to nominate specific web features for prioritized cross-browser implementation. This call for proposals marks the beginning of a rigorous selection process designed to address long-standing fragmentation across major browser engines, including Chromium, Gecko, and WebKit.
The Evolution of the Interop Initiative
The Interop project was conceived as a direct response to a recurring pain point for web developers: the inconsistency in how different browsers interpret and render the same web standards. Historically, developers have struggled with "browser quirks," where a feature works flawlessly in one environment but fails or renders unexpectedly in another. Since its inception, the initiative has successfully mobilized browser vendors to focus their engineering resources on a shared list of priorities.
By aligning the development roadmaps of major engines, Interop has dramatically reduced the time required for new specifications to reach stable, cross-browser support. This collaborative model has evolved significantly since the early days of individual browser efforts. Today, it functions as a highly structured, data-driven project that relies on the Web Platform Tests (WPT) repository as its primary metric for success.
The Proposal Process and Selection Criteria
The window for submitting feature requests is open until September 23, 2026. Interested parties are encouraged to use the official GitHub repository for the Interop project to submit their nominations. However, the organizers have emphasized that not all suggestions will be accepted. The selection committee applies a stringent set of criteria to ensure that the chosen features are ready for widespread adoption.
A "good" proposal, according to the official guidance, must meet several key thresholds. First, the feature in question must have a stable specification. This prevents the project from focusing on experimental or volatile technologies that are still undergoing significant changes. Second, there should be no major, unresolved objections from any of the participating browser vendors. This consensus-driven approach ensures that once a feature is selected for the Interop focus list, the engines are already committed to the work.

Furthermore, proponents are expected to provide evidence of a robust test suite. Because the success of the project is measured by the percentage of tests passed across browsers, a feature without sufficient test coverage is rarely a viable candidate. The project team encourages contributors to consult the Proposal Guide, which outlines additional signals—such as developer demand and industry use cases—that can improve the likelihood of a proposal being selected for the 2027 roadmap.
Reflecting on Interop 2026 Progress
As the industry looks toward 2027, the current state of Interop 2026 serves as a benchmark for success. Recent data from the Interop 2026 dashboard reveals that all major browser engines have made substantial progress toward the goal of 100% interoperability. As of early September 2026, browser performance metrics are significantly higher compared to the same period in 2025.
The 2026 cohort of features was heavily influenced by direct feedback from the developer community. Major industry surveys, such as the State of CSS, and ongoing discussions within the developer signals repository, were instrumental in selecting the focus areas. By prioritizing features that developers actually use in production, the Interop initiative has effectively bridged the gap between theoretical standards and practical application.
Data-Driven Development: Using the Ecosystem Tools
To assist in the proposal process, developers are encouraged to utilize resources like webstatus.dev, which provides real-time visibility into the implementation status of various web features across engines. This tool allows users to identify "low-hanging fruit"—features that are partially implemented in most browsers but lack the final push to achieve full interoperability.
Additionally, the developer signals repository remains a critical resource. By reviewing open issues and tracking community reactions (such as "+1" counts and detailed use cases), potential proposers can build a data-backed case for their suggestions. This approach removes the guesswork from the selection process and ensures that the project’s finite resources are directed toward the features that provide the highest utility to the global developer community.
The Broader Impact on the Web Ecosystem
The implications of the Interop project extend far beyond mere convenience for developers. By fostering a more consistent web, the initiative lowers the barrier to entry for building web-based applications. When developers can rely on consistent behavior across browsers, they spend less time on "defensive coding"—writing workarounds for specific browsers—and more time on innovation and performance optimization.

From a business perspective, the impact is equally significant. Companies that rely on web platforms for their core services benefit from reduced testing costs and shorter development cycles. Furthermore, the collaborative nature of the project reinforces the web as a single, unified platform rather than a fragmented landscape of competing proprietary environments.
Roadmap and Future Outlook
Following the closure of the proposal window on September 23, the selection process will enter a phase of deliberation. During this time, the project stakeholders will review the submissions, weigh them against the established criteria, and engage in technical discussions to finalize the list for 2027. This process is transparent, with all discussions occurring in public repositories, ensuring that the community can follow the rationale behind each decision.
For those who do not have a specific feature to propose, there is still an opportunity to contribute to the project’s success. The organizers emphasize the importance of community engagement: by reviewing existing proposals, offering feedback, and signaling support through comments and reactions, developers play an active role in shaping the priorities of the browser vendors.
As the industry moves toward 2027, the goal remains the same: a more reliable, performant, and consistent web. With the momentum generated by previous years, the upcoming cycle is expected to further refine the web platform, making it a more robust foundation for the next generation of digital experiences. The success of this project is a testament to what can be achieved when the web community and browser vendors align their efforts toward the shared goal of an open, interoperable, and developer-friendly web.
Conclusion
The opening of the Interop 2027 proposal cycle is a critical milestone for the web development ecosystem. By leveraging developer signals, adhering to rigorous standards, and maintaining a transparent selection process, the project continues to demonstrate the efficacy of collaborative engineering. Developers and stakeholders have until September 23, 2026, to contribute their expertise and help define the trajectory of the web for the coming year. Whether through proposing new features or supporting existing ones, the community’s involvement is the engine that drives the web forward. The progress made to date suggests that the future of web development is increasingly defined by cooperation, ensuring that the platform remains the most powerful and versatile tool in the digital age.




