Interop 2026 is now open for proposals!

This is your chance to tell browser-makers which well-defined, well-tested features you wish had better support across browsers.

⬇️ Here's how ⬇️
https://github.com/web-platform-tests/interop/blob/main/proposal_guide.md

Note: this is only for features that are already fully designed & specified. If you have ideas for entirely new features, you can still propose those on GitHub projects related to the feature, e.g https://github.com/whatwg/html/ for HTML, and https://github.com/w3c/csswg-drafts/ for CSS.

@jaffathecake This is your chance to tell browser-makers which well-defined, well-tested features you wish had better support across browsers… and for them to ignore you and do what they’d already planned to do anyway 😒
@paulrobertlloyd what do you feel was ignored last year?
@jaffathecake Speak to @Richr about the countless typography issues that are ignored. Or the poor support for voice styles. Any spec that wasn’t written in the last 3 years is seemingly ignored, the whole thing seems to be less about interoperability but implementing the new hotness.
@paulrobertlloyd @jaffathecake @Richr Agreed! Multicolumn could use a lot of attention, print-stylesheets are also unpredictable. And what about the ridiculous oklch implementation, which is _still_ not fixed. Implemented in a hurry, and just left there.
@vasilis please make proposals for these things, and send me the links so I can follow-up

@jaffathecake @vasilis Here you go Jake. 5 #interOp submissions in order of priority.

https://clagnut.com/blog/2445

My requests for Interop 2026

It’s the time of year again when browser makers ask which shiny new features they should implement in preference to fixing outstanding bugs. Despite my cynicism, I’m trying again with these submissions. They’re mostly typographic but in some cases important.

@Richr @vasilis ohhhh, thanks for making this a blog post too!