The Interop project, the joint effort by Apple, Google, Igalia, Microsoft, and Mozilla to make browsers agree on what the web platform does, has opened its call for 2027 proposals. The window runs through September 23. A proposal needs a stable specification, no outstanding objection from a browser vendor, and test coverage. The 2026 scores as of this month are Chrome 98, Edge 98, Firefox 96, and Safari 92, which is the project working as intended.
I have watched this window open and close for several years, and I think most product teams waste it. They wait for the scope announcement in February, read it, and adjust their plans to whatever the browsers decided to fix. The three weeks when they could have influenced that decision pass without anyone noticing.
The thing that makes a proposal credible is not eloquence. It is a real bug in a real product: this feature behaves differently in two browsers, here is the test, here is what it costs us. Every front-end lead running a large application has a list of those. The design system team has a longer one. Filing one, or adding a real-world case to one that exists, is an afternoon of work, and it is the only moment in the year when a product team can move what the browsers work on next.
My view is that it should be on the front-end lead's calendar every September, the way a release is. The browsers are asking what hurts. Most of us never answer.
What is the one cross-browser bug your team has worked around the longest?
Photo source: https://photos.robertstowe.com/dolomites