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
When the combobox is set to autocomplete="both", it is changing its value to equal the item that autocompletes. This causes other items that should match the entered text to be filtered out.
So I think I have an understanding of why the combobox behaves the way it does, and it basically involves us putting in some workarounds to make the combobox behave more like a text field, which FAST wasn't ready (or willing) to do. Unfortunately, we just had an oversight resulting in this bug, which the fix for is, annoyingly enough, likely going to involve some more state management for the filter text.
🔦 Context
This was originally reported as an SLE bug: Bug 2670859: Nimble combo box | Drop down does not filter the matched text correctly
That will likely be fixed by migrating to a filterable select. Another possible workaround is to use autocomplete="list".
🌍 Your Environment
Not environment-dependent
The text was updated successfully, but these errors were encountered:
My understanding of our intended direction is to align the filter-mode / autocomplete modes with the select. We shouldn't have an autocomplete mode both anymore, effectively just list with improved filtering that aligns with select.
Is there a specific use-case for autocomplete mode both or mode inline? Can we pre-emptively mark it deprecated and say only list should be used?
I started working on item 1 in #2376 and item 2 in this SLE PR. But I ran into a bug with the remaining autocomplete mode "list": #2378. Temporarily marking this blocked because I don't think we want to tell clients to migrate to "list" with that known bug still open.
🐛 Bug Report
When the combobox is set to
autocomplete="both"
, it is changing its value to equal the item that autocompletes. This causes other items that should match the entered text to be filtered out.💻 Repro or Code Sample
autocomplete
toboth
and choose "Many options"Screen.Recording.2024-08-15.at.9.02.05.AM.mov
🤔 Expected Behavior
All of the "Sue..." items should be visible
😯 Current Behavior
Only the first matching item, "Sue (1)", is visible.
💁 Possible Solution
@atmgrifter00 says
🔦 Context
This was originally reported as an SLE bug: Bug 2670859: Nimble combo box | Drop down does not filter the matched text correctly
That will likely be fixed by migrating to a filterable select. Another possible workaround is to use
autocomplete="list"
.🌍 Your Environment
Not environment-dependent
The text was updated successfully, but these errors were encountered: