Repository navigation
Release v4.11.1
Summary
A filtered Dropdown could narrow to the option you wanted and make it keyboard-active with ArrowDown, but Enter did not finish the job: the filter text stayed as typed, the list stayed open, and aria-expanded stayed true. The value was reported, but the selection never landed. Keyboard-only users could not pick an option at all.
Closing the list and settling the filter text was left to the value the application sends back in. An application that does not feed the emitted value straight back, or that answers with a value none of the options carry, never got either — and had no way to do it itself, because the Dropdown exposes neither open state nor input value. The Dropdown now completes the selection it started.
No CSS changed and no markup changed. An application that already feeds the value straight back renders identical DOM before and after. Where the value is not fed back, the Dropdown now renders the selection it committed — filter text, trigger label, data-selected, and the clear action when showClear is set — instead of the stale filter text it used to leave behind. That is the fix, and it is a visible difference for anyone who was living with the defect.
Fixed
- A filtered
Dropdownnow commits the option ArrowDown or ArrowUp made active: Enter reports it once, closes the list, and shows its label. Escape still dismisses without changing the selection (#239) - A
Dropdownselection now closes its own overlay and settles its own filter text, instead of waiting for avaluethat may never come back or may resolve to none of the options (#239) - An unfiltered single-select
Dropdownnow shows the label of the option that was chosen, rather than keeping its placeholder, when the application does not bind the value back (#239)