There's an ideal set of sizing constraints for custom <select>, but the CSS is a bit tricky.
Here's how to make it work, and a tour of new CSS features along the way.

@jakearchibald.com
Developer of sorts at @webdevs.firefox.com, but this is my personal account. No thought goes unpublished. He/him.
There's an ideal set of sizing constraints for custom <select>, but the CSS is a bit tricky.
Here's how to make it work, and a tour of new CSS features along the way.
My goal with the project is for that to happen less. I was sad custom select didn't get picked last year, but browsers worked on it anyway, soooooo ok.
Going through the Interop list of features interop-rank.fxdx.dev and selecting and ranking the ones I want to see across browsers in 2027.
I chose 15 features.
At the top of my list are #HTML #a11y features `focusgroup`, ariaNotify(), `headingoffset` and `headingreset`.
I blogged about my picks for the Interop 2027 project: www.sarasoueidan.com/blog/interop...
inspired by @vale.rocks @pawelgrzybek.com @tylersticka.com @ohhelloana.blog and others who have blogged about their rankings.
Eh no it just means I haven't found the right way to signal it
Basically, UI is hard
It just keeps on savin'. You can update it as much as you want until the deadline, which is some date in early November that I haven't figured out yet
Exactly! π―
I ignored it tbf, and so have many others π
We intend to share the individual rankings with the cross-browser Interop team for analysis, but without the associated Github data (ids, name, username, avatar URL).
Oh yeah it'll still be open then. I did look at other login methods, but didn't find anything particularly good. What login method would have worked better for you?
We'll close it sometime around 13th November, but early data is useful to us for Interop meetings & prep.
I'm glad folks find it useful! I had the idea for it last year, but didn't have time to implement it.
I'm really glad we're running this again. It helped us prioritise a lot of work this year. The previous method was π on GitHub issues, which (imo) is too easily gamed, either intentionally or unintentionally.
FOMO over recent conferences? Or even from last year? Join us next month in Brighton for 2026.ffconf.org - join your peers, join the conversations you can't have with your chatbot, join us for 8 amazing talks and one superb day.
Get your ticket today, don't FOMO-FFCONF.
My personal brain wants some things but my work brain wants others.
So I was forced to blog about it:
That's fair. I guess I just want more people to have that experience, and to see those talks. But yeah, if I think about things like stand up comedy, I'd rather go to a bunch of smaller gigs than one stadium gig.
What do you want us to work on in 2027?
Here's a web app where you can rank the Interop proposals you care about, giving us data we can use to prioritise feature development.
And I wonder where you can see @cydstumpel.nl talk next π€ ::cough:: FFConf ::cough:: π₯³ (also heard great things about Dark Mode)
JPEG XL decoding never landed in Chrome previously, so it never left. There was a version behind a flag a while back, but it wasn't good enough (eg no progressive rendering support).
This was such a fun conference, and all the talks were brilliant. Events like this should have 10x the audience.