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
The top input does not use numbers mode. Observe that typing "Røen" matches one item
The bottom input uses numbers mode. Typing "Røen" shows no matches.
Expected behavior
The matching name is highlighted and is part of the filtered result set.
The codesandbox example also includes an account number formatted in different ways. This is to illustrate why we are using numbers mode here. In the top version typing "12345678901" only matches the first account, but the bottom one matches all three.
Eufemia Version
Browser JS: 10.56.0 Browser CSS: 10.56.0
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
When using an Autocomplete component with
search_numbers
set totrue
, non-alphanumeric characters like "ø" are not matched.To Reproduce
Steps to reproduce the behavior:
<Autocomplete />
withsearch_numbers={true}
, and a data set that contains a string withø
insideHere's a code sandbox demonstrating this issue:
https://codesandbox.io/p/sandbox/stoic-feather-8ymh7s
The top input does not use numbers mode. Observe that typing "Røen" matches one item
The bottom input uses numbers mode. Typing "Røen" shows no matches.
Expected behavior
The matching name is highlighted and is part of the filtered result set.
The codesandbox example also includes an account number formatted in different ways. This is to illustrate why we are using numbers mode here. In the top version typing "12345678901" only matches the first account, but the bottom one matches all three.
Eufemia Version
Browser JS: 10.56.0
Browser CSS: 10.56.0
The text was updated successfully, but these errors were encountered: