You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This GitHub issue is for collecting web developer signals for Customizable <select>.
The <select> element's appearance, including the button, selected option, picker dropdown, and options, can be customized using CSS.
Browser support
Chrome 135 (Apr 1, 2025)
Chrome Android 135 (Apr 1, 2025)
Edge 135 (Apr 4, 2025)
Firefox: not supported
Firefox for Android: not supported
Safari 27 (Sep 14, 2026)
Safari on iOS 27 (Sep 14, 2026)
Give us feedback
If you're pressed for time, but you want this feature to be available in all browsers, please give this issue a thumbs up 👍 reaction.
However, a much better guide for us is to know how you'd use this feature, and what you're having to do in the meantime. This helps us judge the priority versus other features.
Copy the template below in a comment, and add the details that matter to you.
## What I want to do with this feature<!-- Add your specific use-cases, even if they seem obvious to you. -->## What I'm having to do in the meantime<!--Are you having to use another feature instead, a polyfill, or is it blocking you completely?Why are the alternatives worse than using this feature?-->
Reacted by Nilesh Prajapati, Sacha Greif, Grant Gryczan, Jakob2o, Dimox, Alex Riviere, Marieme Azib, Sean van Zuidam, ThainBBdL, LX and 264 more
Reacted by Marieme Azib, Jayden Pearse, Freddy M Huaylla Silvestre, Duki, JuanPastenCastillo, Sebastian Zartner, Garrett Kocian, Jo, Peter, Humberto Filho and 10 more
I have a personal tasks and notes management app I work on. In this app, I can select a new status for a task via a custom dropdown that displays status icons. Dozens of these selectors can appear on the page at once.
What I'm having to do in the meantime
I'm having to create a custom JavaScript-driven component, using CSS anchor positioning to position it. It's been up to my to ensure all the relevant accessibility features of a native <select> element are implemented in this custom JavaScript.
I develop and maintain a newer version of Piskel, Piskel Sharp. I'm always up to using the latest CSS features for the app to modernize the UI, and this is one of the features I am interested in utilizing. It makes styling <select> elements much easier rather than having to use the default. Firefox is the main holdup, I'm not sure how many people would use it (as the app is packaged using NW.JS; an online hosted version is available on the Multi-Bit-Catalogue), but I don't want to ruin the page's formatting because of it.
What I'm having to do in the meantime
A technique I've seen from other developers, creating their own selectors using inputs and lists. This is what I am currently using:
<labelstyle="display: block; text-align: center;">
Color Format
<inputtype="checkbox" id="color-format-toggle" class="dropdown-toggle"><labelfor="color-format-toggle" class="dropdown-header"><spanid="current-color-format-display" class="current-value">Hex</span><spanclass="arrow">▼</span></label><ulclass="dropdown-options color-format-options"><li><buttontype="button" data-value="hex">Hex</button></li><li><buttontype="button" data-value="rgb">RGB</button></li></ul></label>
Activity
[-]Customizable <select>[/-][+]Customizable <select>[/+]Cipscis commentedon Sep 30, 2026
What I want to do with this feature
I have a personal tasks and notes management app I work on. In this app, I can select a new status for a task via a custom dropdown that displays status icons. Dozens of these selectors can appear on the page at once.
What I'm having to do in the meantime
I'm having to create a custom JavaScript-driven component, using CSS anchor positioning to position it. It's been up to my to ensure all the relevant accessibility features of a native
<select>element are implemented in this custom JavaScript.That-One-Bit commentedon Nov 19, 2026
What I want to do with this feature
I develop and maintain a newer version of Piskel, Piskel Sharp. I'm always up to using the latest CSS features for the app to modernize the UI, and this is one of the features I am interested in utilizing. It makes styling
<select>elements much easier rather than having to use the default. Firefox is the main holdup, I'm not sure how many people would use it (as the app is packaged using NW.JS; an online hosted version is available on the Multi-Bit-Catalogue), but I don't want to ruin the page's formatting because of it.What I'm having to do in the meantime
A technique I've seen from other developers, creating their own selectors using inputs and lists. This is what I am currently using: