September 3, 2026 — By Rachel Andrew
The web development community has officially entered a crucial period of collaboration and planning. Today marks the launch of Interop 2027, the latest iteration of a landmark multi-vendor initiative designed to fix the web’s most persistent inconsistency issues across browsers.
As in previous years, the project opens its doors to the public with a formal call for proposals. Developers, engineers, and stakeholders across the globe now have a direct channel to influence which web platform features will be prioritized, tested, and pushed toward cross-browser standardization next year.
The proposal window is open immediately, but participants must act quickly. Submissions will close on September 23, 2026, after which a rigorous selection process will begin to shape the final lineup for Interop 2027.
Main Facts: What is Interop 2027 and Why Does It Matter?
The Interop project is an unprecedented cooperative effort involving major browser engines—including Chromium (Google/Microsoft), Gecko (Mozilla), and WebKit (Apple)—alongside independent contributors and developers. Historically, one of the greatest friction points for web developers has been cross-browser inconsistency: a feature that works seamlessly in Chrome might behave unpredictably in Safari or fail to render in Firefox.
Interop aims to eliminate these inconsistencies by focusing collective energy on specific web platform features that have already cleared initial standards committees but suffer from fragmented implementation.
Key Takeaways from the Launch:
- The Goal: Drive web platform features toward 100% interoperability across all major browsers.
- The Timeline: The submission period runs from September 3 to September 23, 2026.
- The Process: Following the deadline, all submitted proposals will be evaluated using a transparent, community-vetted selection framework.
- Who Can Participate: Anyone from enterprise software engineers to indie web developers can submit a proposal, vote on existing ideas, or review criteria via the Web Platform Tests (WPT) GitHub repository.
Chronology: The Journey from Past Successes to the 2027 Launch
To understand where Interop 2027 is heading, it is helpful to look at how the initiative has evolved and where the current ecosystem stands.
Early 2026: Setting the Stage with Interop 2026
At the start of 2026, the Interop steering committee unveiled that year’s focus areas, heavily informed by developer pain points highlighted in industry surveys like The State of CSS and the developer signals repository. These insights ensured that the features chosen for Interop 2026 were not selected in a vacuum, but rather represented the absolute highest-demand tools requested by daily web creators.
September 3, 2026: The Launch of Interop 2027
The project officially kicks off its planning cycle today. Opening the floor early in September gives the community, browser vendors, and working groups ample time to debate, refine, and champion feature requests before the September 23 deadline.
September 23, 2026: Proposal Deadline (Upcoming)
Once submissions close, the organizing bodies will begin filtering proposals based on technical readiness, stability, and available testing infrastructure.
Late 2026 and Beyond: Selection and Execution
Following the evaluation phase, the final feature set for Interop 2027 will be locked in, paving the way for a year of intense engineering, test writing, and cross-browser scoring tracked publicly on live dashboards.
Supporting Data: Progress on Interop 2026 and How to Measure Success
As developers prepare proposals for Interop 2027, the current state of Interop 2026 demonstrates the incredible momentum the initiative has generated.
Current Interop 2026 Dashboard Metrics
Data from the official Interop 2026 dashboard illustrates a massive leap forward in browser cooperation. As of early September 2026, all major experimental browser builds are performing exceptionally well in passing standardized web-platform tests:
- Chrome (Experimental): 98%
- Edge (Experimental): 98%
- Firefox (Experimental): 96%
- Safari (Experimental): 92%
Compared to historical timelines where browser compatibility could lag by years, these scores indicate that the Interop framework is actively accelerating the rate at which web standards become universally reliable.
What Makes a Winning Proposal?
Not every web feature is ready for the Interop spotlight. To ensure that selected projects are viable, proposals must meet stringent baseline requirements:
- A Stable Specification: The feature must already have passed through the foundational standards process. Ideas that are still in early draft form or subject to massive architectural shifts are typically excluded.
- No Outstanding Vendor Objections: A successful proposal cannot be heavily contested by one or more browser engine maintainers. Consensus is vital.
- Prior Implementation (Preferred): Historically, features that perform best in Interop have already been partially or fully implemented in at least one browser.
- A Robust Test Suite: Success in Interop is quantified by passing automated Web Platform Tests (WPT). Therefore, a proposal must be backed by an existing, high-quality test suite—or feature a clear path to developing one.
Developers looking for inspiration or validation can utilize tools like webstatus.dev to analyze feature support across platforms, or reference the developer signals repository to review documented use cases and community backing.
Official Guidelines and Strategies for Submitting Proposals
For those looking to craft a compelling pitch for Interop 2027, project maintainers have provided explicit documentation to guide the process.
Utilizing the Proposal Guide
The official Proposal Guide outlines several "signals" that can dramatically boost a proposal’s chances of selection. These include high developer demand, clear alignment with modern web application needs, and quantifiable pain points solved by standardization.
According to the project organizers:
"The Interop project aims to take things that have already been through the standards process, and make them interoperable. Therefore, the first thing to consider is whether your idea has a stable specification, and no outstanding objections from one or more browser vendors."
How to Get Involved Beyond Submitting
Not every developer has a brand-new feature to pitch, and that is entirely normal. The broader community plays an equally vital role in determining the final lineup:
- Audit Existing Proposals: Browse the growing list of submissions on the official GitHub repository.
- Engage and Validate: Upvote, comment on, and discuss the submissions you believe will have the most positive impact on your daily workflow.
- Spread the Word: Share the call for proposals across social media, internal engineering teams, and local developer meetups to ensure diverse global representation.
Implications: What Interop 2027 Means for the Future of Web Development
The continuation of the Interop initiative through the announcement of Interop 2027 signifies a mature, cooperative era in web browser development. Gone are the days of the "browser wars" where proprietary implementations fragmented the web and forced developers into endless cycles of writing browser-specific hacks.
1. Reduced Technical Debt
When features become fully interoperable, development teams no longer need to maintain complex polyfills or write conditional CSS and JavaScript to handle edge cases in individual browsers. This directly translates to leaner codebases, faster load times, and reduced maintenance overhead.
2. Predictable Progressive Enhancement
With all major vendors aligning their implementation roadmaps with Interop targets, developers can adopt cutting-edge layout, graphic, and programmatic features with confidence, knowing that their users will receive a consistent experience regardless of whether they browse on mobile, desktop, corporate enterprise hardware, or consumer devices.
3. Community-Driven Governance
By opening the selection process directly to the public via GitHub and developer signal trackers, the web platform remains democratic. The features prioritized for Interop 2027 will not be dictated solely by corporate roadmaps, but by the actual pain points experienced by the millions of developers building the modern internet every day.
Take Action Today
The clock is ticking toward the September 23 deadline. Whether you want to champion a specific CSS module, a JavaScript API, a DOM feature, or simply wish to voice your support for existing proposals, your participation helps build a more cohesive web.
- Submit Your Ideas: Visit the Interops GitHub Issues Page to file your proposal.
- Review the Rules: Read through the Selection Process Documentation to understand how submissions are filtered.
- Track Progress: Keep an eye on wpt.fyi to watch the evolution of browser testing metrics in real time.
Join the conversation, make your voice heard, and help shape the foundation of the web platform for 2027 and beyond.
