
道Dojo · · 3 min read
You can finally style the dropdown. Bin the library
Since Safari 27, the real select element can be styled freely in Chrome and Safari. Why home-made dropdowns should go now, and what to watch out for.
The samurai fills in forms using only the Tab key; gauntlets and trackpads don't get along. On a home-made country dropdown, that takes him straight to the footer.
That isn't an armour problem. It's the problem with nearly every dropdown rebuilt from div elements and JavaScript because the real <select> didn't match the design. It looks like a picker, but for keyboards and screen readers it is often just decoration.
The good news: you'll soon have no reason to build the imitation.
What changed
Chrome has let you style the native <select> fully with CSS since version 135 (Chrome for Developers, 24 March 2025). Safari 27 shipped on 14 September 2026 (Apple), and according to the WebKit team (8 June 2026) it includes customizable select. MDN's compatibility data lists Safari on the iPhone as well. So Chrome, Edge and Safari support it. According to MDN, Firefox only has it behind a configuration flag so far.
How it works:
appearance: base-selectonselectand::picker(select)resets the browser look. From there, you style freely.::picker-iconis the arrow,::checkmarkthe tick next to the selected option. Both can be replaced.<selectedcontent>shows the current choice in the closed field, icons or flags included.
The key sentence is on the WebKit blog: because it is still a real <select>, keyboard navigation and screen reader support keep working. You get the look from the mock-up and the behaviour from the browser.
Figma comment on frame "Contact": "Dropdown as designed please, not Windows 98." Resolved by: Safari 27.
Our view: bin the library, but use judgement
If you are building a form today, stop assembling your own dropdown. Every line of JavaScript that imitates a picker has to rebuild focus, arrow keys, type-to-jump and screen reader announcements by itself. Usually something is missing.
Three things to know:
- Firefox sees the plain field for now. That's not a bug, it's the plan. Browsers that don't know
base-selectshow a working standard dropdown. Less pretty, fully usable. - Go easy on mobile. According to the Chrome team,
base-selectdrops the mobile operating system's built-in picker. For a long list of countries, the native wheel may be the better choice. You can limit the new look to larger screens with a media query. - Test with the keyboard. Even a real
<select>can be styled into uselessness, for example by designing away the focus ring.
In our website projects, this is exactly the kind of detail that should come up at sign-off, before visitors find it.
This week's drill
Open the most important form on your website: contact, enquiry or checkout. Click into the first field and move only with Tab, the arrow keys and Enter until you submit. If a dropdown won't open, won't respond to the arrow keys, or the focus skips right over it, it's an imitation. Note where it is, and at the next update ask whether it can be replaced with a real <select>.
If you end up in the footer, you now know how the samurai feels.
道場Dojo