[MultiCombobox]: [Missing input events for multi-character Chinese/Japanese typing]

[Pranjal-98]

Describe the bug

When typing Chinese or Japanese text using an IME inside the MultiComboBox, only the first character triggers an input event. Subsequent characters typed during the same IME composition are not detected.

In native and other UI5 controls like and , IME updates fire continuous input events. However, MultiComboBox does not handle these composition updates, causing filtering and suggestions to stop working after the first CJK character.

Consistency across UI5 controls is essential for proper internationalization and accessibility, so this issue requires alignment with expected IME input behavior.

Isolated Example

No response

Reproduction steps

1. Render a simple multicombobox with a few items.
2. Open the browser console to observe input-related events.
3. Type a multi-character Chinese or Japanese word using an IME (e.g., 技能, 問合せ).
4. Notice that only the first character fires an input / ui5-input event.

Expected Behaviour

The MultiComboBox should fire input events for every update during IME typing, just like other UI5 input controls. Filtering and suggestions should continuously update as the user types multiple Chinese or Japanese characters, not only after the first character.

Screenshots or Videos

No response

UI5 Web Components for React Version

2.16.0

UI5 Web Components Version

2.16

Browser

Chrome

Operating System

No response

Additional Context

No response

Relevant log output

Organization

SAP Labs

Declaration

• [x] I’m not disclosing any internal or sensitive information.

[MarcusNotheis]

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

[Vonahz]

Thanks for the report! To help us investigate, would you mind providing a simplified or isolated sample that reproduces the issue?

[github-actions[bot]]

Hello, everyone! The issue has been inactive for 21 days. If there are still questions or comments, please feel free to continue the discussion. Inactive issues will be closed after 7 days!