[FEE-11302] Customizable <select> — CSS-Styleable Select
Limited Availability
Chrome 135+. Not yet available in Firefox or Safari. Use as progressive enhancement only.
Context
For most of the web's history, <select> has been the element that CSS could not touch. You can change its font and maybe its border. The dropdown panel, the arrow indicator, the option rows, the padding, and the hover state belong to the operating system. Every major design system has run into this wall and made a choice: accept the native look, or throw away the <select> entirely.
Why <select> resists styling
<select> is a replaced element. The browser delegates its rendering to the platform UI toolkit: Win32 ComboBox on Windows, NSPopUpButton on macOS, GtkComboBox on Linux. The browser's CSS engine renders the box model around the widget, but the widget's interior is a black box. CSS properties that work on every other element, such as background-color, border-radius, padding, and color on hover, have no effect on the rendered widget.
This architectural decision made sense in the early web. Form controls that matched the OS gave users a familiar, accessible experience. The platform handled keyboard navigation (arrow keys to move through options, Enter to confirm, Escape to dismiss), screen reader announcements, and focus management. Developers got all of that for free.
The cost was that design systems could not put their fingerprint on these controls. A button, a checkbox, an input: all styleable. The dropdown was not.
The appearance: none era
Browsers eventually exposed appearance: none, which suppresses the native widget rendering and gives CSS more control. But appearance: none on a <select> is a partial escape: you can style the closed state (the box, the arrow you draw yourself), but the dropdown panel (the list of options) remains uncontrollable. The panel still renders as a native OS overlay; CSS cannot reach it.
Developers discovered this the hard way. Many tutorials taught appearance: none as if it made <select> fully styleable. It does not. The panel is untouched.
The custom dropdown workaround
The response from the frontend community was to stop using <select> altogether. The pattern: a <div> (or a <button>) that looks like a select box, paired with a hand-rolled list of <li> items that appear on click, styled to match the design system, tracked by JavaScript event listeners that close the list when the user clicks outside.
This pattern works visually. The accessibility cost is enormous:
- The
<div>has no native role. Developers must addrole="combobox",aria-haspopup,aria-expanded,aria-activedescendant, andaria-controlsmanually, and keep them synchronized with the open/close state. - The
<li>items must haverole="option"andaria-selected. - Keyboard navigation must be reimplemented in JavaScript: arrow keys to move selection, Enter to confirm, Escape to close, Home/End for first/last.
- The element does not participate in native form submission. Developers must add a hidden
<input>and keep it synchronized with the selected value. - Mobile browsers will not open the native picker. On iOS, a native
<select>opens the scroll-wheel picker. A custom dropdown does not.
Every one of these is something the browser already does for a real <select>. The custom dropdown is an accessibility and maintenance liability masquerading as a design improvement.
The open UI initiative and appearance: base-select
The Open UI Community Group at the W3C spent years cataloging how design systems use select components and proposing a path to make native <select> styleable without sacrificing accessibility. The result (currently being implemented in Chrome 135+) is a new rendering mode activated by appearance: base-select.
When appearance: base-select is set on a <select>, the browser:
- Stops delegating rendering to the OS widget layer.
- Exposes the dropdown panel via the
::picker(select)pseudo-element, which CSS can now style withbackground,border-radius,box-shadow, and more. - Supports a new
<selectedoption>HTML element that the browser uses to render the collapsed (closed) state of the select, allowing rich custom markup. - Maintains the full keyboard navigation contract: arrow keys, Enter, Escape, Home/End.
- Preserves the ARIA
comboboxrole and all associated accessibility properties.
This is the native <select>, not a custom dropdown. Form submission still works. The mobile native picker still works (on platforms that support it). Screen readers still announce the role, state, and selected option.
You are building a design system component library. The token for interactive controls calls for a brand-blue #0057FF focus ring, a 12px border radius on all dropdowns, a subtle box-shadow on the picker panel, and a custom arrow indicator using an SVG from the icon system. Existing inputs, buttons, and checkboxes already follow this token. Only <select> lags behind.
Requirements:
- The collapsed select box must use the design token border radius and colors.
- The dropdown panel must have the brand box shadow and border radius.
- The custom SVG arrow must replace the browser's native indicator.
- The component must remain a native
<select>, not a custom ARIA widget. - The component must work with existing
<form>elements without JavaScript wiring for form submission. - In Firefox and Safari, the component must degrade gracefully to the default native
<select>appearance.
Before appearance: base-select, requirement three (custom arrow) is achievable, but requirement two (panel shadow/radius) is not: the dropdown panel is inaccessible to CSS. A fully compliant design token implementation requires a custom ARIA dropdown, which breaks requirements three through five in different ways.
With appearance: base-select and progressive enhancement via @supports, all six requirements are satisfiable in Chrome 135+ while degrading cleanly to native on other browsers.
Best Practices
- MUST wrap all
appearance: base-selectstyles in@supports (appearance: base-select). In unsupporting browsers, the rule is unknown and falls through to the native<select>rendering, which is the correct fallback. - MUST keep
<selectedoption>content synchronized with the selected<option>in Chrome's current implementation. The browser does not yet mirror option content automatically on dynamic changes; achangeevent listener and an initial synchronous call are both required. The listener handles subsequent changes, and the initial call populates the element on page load. - MUST preserve keyboard navigation. Do not attach
keydownlisteners that intercept arrow keys, Enter, or Escape on the<select>element; the browser owns this contract and overriding it breaks screen reader and keyboard-only workflows. - MUST verify that
role="combobox"is preserved after applyingappearance: base-select. Open DevTools Accessibility panel and confirm the computed role; do not suppress it by adding a conflictingroleattribute. - SHOULD test with screen readers (NVDA on Windows, VoiceOver on macOS/iOS). Navigate to the select with Tab, open it with Space or Enter, and verify that the reader announces "collapsed" and "expanded" states and reads each option as you arrow through.
- SHOULD NOT use
::picker(select)styles for layout decisions that would be broken or visually wrong in browsers that do not support it. Since::picker(select)is inside the@supportsblock, non-supporting browsers never see these styles; make sure the fallback layout is independently correct. - SHOULD NOT style
<option>elements with complex CSS inside::picker(select). Option styling support within the picker is limited in Chrome 135; test thoroughly and use simple properties (color,background,padding). - MAY place rich HTML (icon + label) inside
<selectedoption>and the matching<option>. Chrome renders the<selectedoption>in the collapsed box and the<option>content in the picker, so you can have a compact icon-only collapsed state and a full label in the panel. - MAY animate
::picker(select)entry and exit using@starting-style. Chrome supports this for discrete property transitions on the picker overlay.
Example
Branded select with appearance: base-select
A design-system select component with brand colors, a custom SVG arrow, a styled dropdown panel, and progressive enhancement for non-supporting browsers.
HTML
<!-- The <selectedoption> element renders the collapsed (closed) state -->
<label for="sort-select">Sort by</label>
<select id="sort-select" class="brand-select">
<selectedoption></selectedoption>
<option value="name">Name</option>
<option value="date">Date modified</option>
<option value="size">File size</option>
<option value="type">File type</option>
</select>CSS
/* Base styles — visible in all browsers (native select appearance) */
.brand-select {
font: inherit;
font-size: 0.875rem;
padding: 0.5rem 2.5rem 0.5rem 0.75rem;
border: 1px solid #ccc;
border-radius: 6px;
background-color: #fff;
color: #111;
cursor: pointer;
min-width: 160px;
}
.brand-select:focus {
outline: 2px solid #0057ff;
outline-offset: 2px;
}
/* Progressive enhancement: only runs when appearance: base-select is supported */
@supports (appearance: base-select) {
.brand-select {
appearance: base-select;
/* Brand token: 12px border radius */
border-radius: 12px;
/* Custom SVG arrow — replaces browser's native indicator */
background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16'%3E%3Cpath fill='none' stroke='%23555' stroke-width='2' stroke-linecap='round' stroke-linejoin='round' d='M4 6l4 4 4-4'/%3E%3C/svg%3E");
background-repeat: no-repeat;
background-position: right 0.75rem center;
background-size: 16px;
}
/* Style the dropdown panel */
.brand-select::picker(select) {
background: #fff;
border: 1px solid #e0e0e0;
border-radius: 12px;
box-shadow: 0 4px 24px rgba(0, 0, 0, 0.12);
padding: 0.25rem 0;
overflow: hidden;
}
/* Style individual options inside the picker */
.brand-select option {
padding: 0.5rem 0.75rem;
border-radius: 8px;
margin: 0 0.25rem;
cursor: pointer;
color: #111;
}
.brand-select option:hover,
.brand-select option:focus {
background-color: #f0f5ff;
color: #0057ff;
}
.brand-select option:checked {
background-color: #e8f0fe;
color: #0057ff;
font-weight: 500;
}
/* Style the selectedoption element (collapsed state display) */
.brand-select selectedoption {
display: block;
color: #111;
}
}JavaScript — <selectedoption> sync
Chrome's current implementation requires manual synchronization of <selectedoption> when the user changes the selection. Without this, the collapsed state displays stale content after the initial render in some scenarios.
/**
* Sync <selectedoption> with the currently selected <option>.
* Required for Chrome 135's current implementation.
* Safe to run in all browsers — querySelector returns null
* in browsers that do not support the element, and the
* event listener is a no-op if selectedOption is null.
*/
function syncSelectedOption(selectEl) {
const selectedOption = selectEl.querySelector('selectedoption');
if (!selectedOption) return; // browser does not support <selectedoption>
const update = () => {
const chosen = selectEl.selectedOptions[0];
if (!chosen) return;
selectedOption.textContent = chosen.textContent;
};
// Sync on every change
selectEl.addEventListener('change', update);
// Sync on initial load
update();
}
// Initialize all brand selects on the page
document.querySelectorAll('.brand-select').forEach(syncSelectedOption);Progressive fallback check
// Optional: log support status during development
if (CSS.supports('appearance', 'base-select')) {
console.log('base-select: enhanced rendering active');
} else {
console.log('base-select: falling back to native select appearance');
}What this gives you in practice:
- Chrome 135+: branded select with custom border radius, panel shadow, SVG arrow, and styled options.
- Firefox / Safari / Edge (non-Chromium): standard native
<select>rendering that is correct and functional, unaffected by the@supportsblock. - In all browsers: native form submission, native keyboard navigation, native screen reader support.
Rich collapsed state with icon + label
You can place HTML markup inside <selectedoption> to show a richer collapsed display while the <option> elements contain the plain text that is announced to screen readers and used for form submission.
<select id="status-select" class="brand-select status-select">
<selectedoption></selectedoption>
<option value="active">Active</option>
<option value="paused">Paused</option>
<option value="archived">Archived</option>
</select>@supports (appearance: base-select) {
.status-select selectedoption {
display: flex;
align-items: center;
gap: 0.5rem;
}
.status-select selectedoption::before {
content: '';
display: inline-block;
width: 8px;
height: 8px;
border-radius: 50%;
background: currentColor;
}
}const STATUS_COLORS = {
active: '#22c55e',
paused: '#f59e0b',
archived: '#94a3b8',
};
function syncStatusSelect(selectEl) {
const selectedOption = selectEl.querySelector('selectedoption');
if (!selectedOption) return;
const update = () => {
const chosen = selectEl.selectedOptions[0];
if (!chosen) return;
const value = chosen.value;
selectedOption.textContent = chosen.textContent;
selectedOption.style.color = STATUS_COLORS[value] ?? '#111';
};
selectEl.addEventListener('change', update);
update();
}
document.querySelectorAll('.status-select').forEach(syncStatusSelect);Browser Support
| Browser | Support | Notes |
|---|---|---|
| Chrome | 135+ | Full support: appearance: base-select, ::picker(select), <selectedoption> |
| Edge | 135+ | Chromium-based; same support as Chrome |
| Firefox | — | Not shipped as of April 2026 |
| Safari | — | Not shipped as of April 2026 |
Feature detection with @supports:
@supports (appearance: base-select) {
select {
appearance: base-select;
}
select::picker(select) {
border-radius: 12px;
box-shadow: 0 4px 16px rgba(0, 0, 0, 0.15);
}
}Feature detection with JavaScript:
const supportsBaseSelect = CSS.supports('appearance', 'base-select');Production guidance: As of April 2026, appearance: base-select is Chrome 135+ only. Do not use it without @supports progressive enhancement. In browsers without support, the entire @supports block is ignored and the native <select> renders correctly. Firefox and Safari users receive the standard native select, fully functional and accessible. The specification is being developed by the Open UI Community Group; implementation details (especially <selectedoption> sync behavior) may change as other browsers implement the feature.
Related Topics
- FEE-11203 CSS @layer — Cascade Layers. Cascade layers are useful for integrating customizable
<select>styles into a design system: place base-select overrides in acomponentslayer to keep specificity organized and allow per-page overrides. - FEE-11301 field-sizing — Self-Sizing Form Controls. Companion article on CSS form control enhancements;
field-sizing: contenton<select>pairs naturally withappearance: base-selectto create compact, content-driven select widths.
References
- Customizable select element (MDN Web Docs). Primary MDN reference for
appearance: base-select,::picker(select), and<selectedoption>. - Open UI: Customizable
<select>explainer. Open UI Community Group specification and rationale. - CSS Basic User Interface Module Level 5 (W3C Editor's Draft). Specification defining
appearance: base-selectand related properties. - Styling select elements for real this time (Chrome for Developers blog). Practical walkthrough of the feature from the Chrome team, with live demos.
- Can I use: appearance: base-select. Browser compatibility table.