Filter in property value selection list fails with non-ASCII characters (umlauts)

Search first

• I searched and no similar issues were found

What Happened?

When filtering the selection list for node property values, the filter function only works correctly with pure ASCII characters. Filtering for values containing non-ASCII characters, such as German umlauts (ä, ö, ü, ß) or other accented characters, fails: the matching items are either not found at all or return incorrect search results.

Reproduce the Bug

1. Create a property with choice/selection values containing umlauts or non-ASCII characters (e.g., "Überprüfen", "Grün", "Ändern").
2. Open the property selection/filter dropdown.
3. Type an umlaut or a word containing umlauts into the filter/search input.

Observed: Matching items are not filtered correctly, resulting in missing entries or wrong search results.

Expected Behavior

The filter should handle Unicode and non-ASCII characters (like umlauts) correctly, matching and displaying the appropriate property values reliably.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

• Platform: Linux Desktop
• Version: 2.0.1-alpha+nightly.20260917 (DB beta)

Additional Context

Likely caused by a case-insensitivity or string-matching routine that only handles standard ASCII ranges.

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

Reproduce the issue in the property selection/filter dropdown using values such as “Überprüfen”, “Grün”, and “Ändern”. Trace the filter entry point and its string-matching routine, then verify that Unicode and case-insensitive searches return the expected property values on Linux Desktop.