Tevpro insights
Customizable Native Selects With CSS
Learn how to style a real HTML select with appearance: base-select, keep a native fallback, and submit a working form.
Key takeaways
- A customizable select remains a real form control with labels, option values, validation, and native submission behavior.
- appearance: base-select and ::picker(select) provide styling hooks where supported; an ordinary select remains usable elsewhere.
- Test keyboard, touch, assistive technology, and validation in your actual target browsers before replacing a mature control.
A custom-looking dropdown should not discard the useful behavior of a real form control. Start with a labeled select, then opt into the new picker styling only where the browser supports it.
1. Keep the HTML a real select
<label for="region">Region</label>
<select id="region" name="region" required>
<option value="">Choose a region</option>
<option value="north">North</option>
<option value="south">South</option>
</select>
The label names the control, name="region" supplies the submitted field, and required prevents the empty choice. Those behaviors do not depend on the new styling hooks.
2. Add a readable baseline
select {
width: 100%;
padding: .75rem;
border: 2px solid #7e94a8;
border-radius: .6rem;
background: white;
color: #14263e;
}
select:focus-visible { outline: 3px solid #159cc0; }
An unsupported browser keeps its ordinary native picker. The focus outline remains visible in both versions.
3. Style the picker when available
@supports (appearance: base-select) and selector(::picker(select)) {
select, select::picker(select) { appearance: base-select; }
select::picker(select) {
border: 2px solid #7e94a8;
border-radius: .6rem;
box-shadow: 0 12px 30px #14263e30;
}
select option { padding: .7rem 1rem; }
select option:checked { background: #d8f4f1; }
}
appearance: base-select opts the control and picker into the customizable rendering model. ::picker(select) targets the open menu; option:checked identifies the selected row. The option values and form submission stay unchanged. Test keyboard, touch, and assistive technology on the browsers you support before replacing an established dropdown.
Try the complete example below. Open the menu, select a region, and submit the form. Edit styles.css to compare the native fallback with the customizable picker. The picker styling only applies when the browser supports it.
Try a customizable native select
Open the picker, choose a region, and submit. Edit styles.css to test the fallback and the appearance: base-select enhancement in your browser.
For browser compatibility and the full specification, see the primary references in Sources below.
Sources
Why work with us
Why Tevpro?
Whether you’re a startup with a bold product idea or an established company seeking a stronger delivery partner, Tevpro delivers results. Our expert consultants specialize in building secure, scalable applications that simplify operations and drive real ROI.
FAQ
Frequently asked questions
Yes. It keeps a real select, label, option values, form submission, and validation rather than replacing those behaviors with div elements.


