Proposal: Introduce `filter` Attribute for `select`

[sudheer-gowrigari]

The proposed filter attribute for select aims to provide a more efficient, user-friendly way to navigate through long lists of options. This attribute would enable real-time filtering of options based on user input, making it especially useful in scenarios with large datasets.

Proposed Behavior

The 'filter' attribute would allow the select to dynamically filter and display options that match the user's input. This would reduce the number of visible options, helping users to make selections more quickly and accurately.

This proposal also aids the development of the filter attribute for the combobox

[lukewarlow]

Where would the user input be shown if anywhere?

[YummyBacon5]

If this is added, then won't <selectlist> become a duplicate of <combobox>?

Also #847 is about being able to search though options for <selectlist> with an input

[sudheer-gowrigari]

I meant to say: capture user input directly through typing when the selectlist is focused.

[lukewarlow]

If this is added, then won't become a duplicate of ?

For me selectlist is a filterable list for you to pick from. Combobox is a free input with suggestions.

Idk if that's a distinction in the proposal but that's what makes it two different elements in my head.

[TrevorRice]

Would there be any affordance given to users to differentiate between the behavior of a filterable and non-filterable <selectlist>?

[github-actions[bot]]

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.