The Interop 2027 project is accepting proposals through September 23, 2026. Developers, framework authors and standards communities can identify web features whose browser differences still require expensive workarounds.
The short answer
| Criterion | What strengthens a proposal |
|---|---|
| Real problem | Describe a concrete case that fails by browser. |
| Ecosystem impact | Provide issues, surveys or affected site examples. |
| Standard | Point to a sufficiently stable specification. |
| Measurement | Use Web Platform Tests or explain how to create them. |
The final scope is scheduled for publication in early February 2027 after joint review.
Why Interop produces results
The project does not seek a feature exclusive to one browser. It selects areas where engines can converge and tracks progress with shared tests. Previous editions improved View Transitions, anchor positioning, popovers, Shadow DOM and several CSS capabilities.
This method reduces subtle divergences: accepted syntax with different behavior, inconsistent accessibility or events fired in an unexpected order.
Turn frustration into measurable evidence
“Forms differ” is too broad. A strong proposal isolates one API or behavior, provides a minimal reproduction and shows user impact. Include Chrome, Firefox and Safari versions, expected results and specification links.
Then inspect existing WPT coverage. If tests are missing, describe the needed assertions. A measurable problem is more likely to enter a program driven by automated scores.
Frameworks have useful evidence
React, Vue or a polyfill may hide an incompatibility while imposing code, weight and maintenance on thousands of projects. Library maintainers can offer strong impact evidence through download volume, related issues and browser-specific branches.
The proposal should still target the standard platform rather than request support for a framework-specific convention.
What teams can do now
Collect browser-conditioned workarounds in the codebase and rank them by impact. Select one reproducible problem and ask other developers to review the submission. Even an unselected topic can inform Edge's Top Developer Needs work.
Interop is a rare opportunity to address compatibility debt at its source. A concise, documented and testable proposal is more useful than a long list of grievances that cannot be measured.




Join the discussion
Comments
Loading comments…