The <select> element has been the awkward child of web forms for as long as most developers can remember. Style the arrow, maybe the background colour, and then you hit a wall of User Agent styling that browsers kept firmly under their control. The standard answer was always to fake it: build a custom dropdown from <div>s, wire up keyboard navigation by hand, say a quiet prayer for accessibility, and ship it. That era is ending.
What appearance: base-select does
The Customizable Select API pivots on a single CSS property: appearance: base-select. Set it on your <select> and on the new ::picker(select) pseudo-element for the dropdown panel, and the browser steps back from its own styling. From that point it is a regular HTML element — full control over colour, font, size, shadows and the content of each option. You can now put real HTML inside <option> elements: an icon next to the label, a subtitle, a colour swatch. No JavaScript, no ARIA gymnastics — the element retains its built-in form accessibility.
Where cross-browser support stands
Chrome 135 shipped stable support, covering all Chromium-based browsers. Firefox 153, released today, ships the HTML parser change that is the prerequisite for full support: nested elements inside a <select> are now correctly parsed into the DOM instead of being discarded. Safari is prototyping it in Technology Preview. Full cross-browser parity is not there yet, but downward compatibility is solid — browsers without support simply render the native dropdown, unchanged.
How to use it today
The recommended approach is progressive enhancement. Write your form normally, then layer the richer styling inside an @supports (appearance: base-select) block. Users in Chrome and Edge get the improved result; everyone else gets a working form. No library, no clever workarounds, no extra maintenance debt. This is the kind of fix the web community has waited twenty years for — not a workaround, not a polyfill, just the platform doing what it should have done all along.



