[ComboBox]: onChange should provides eventDetail like onSelectionChange event

[gnseo]

Bug Description

onChange is triggered when user selects one of items, but we can not get selected item from event.detail like onSelectionChange event.

I found that it was implemented as following.

webcomponents/packages/main/src/ComboBox.ts

Line 250 in 359fe49

"change": void,

Could you let onChange's event parameter provides event.detail.item like onSelectionChange?

Affected Component

ComboBox

Expected Behaviour

When onChange event is triggered, we should be able to access selected item by event.detail.item.

Isolated Example

No response

Steps to Reproduce

...

Log Output, Stack Trace or Screenshots

No response

Priority

None

UI5 Web Components Version

2.20.2

Browser

Chrome

Operating System

No response

Additional Context

No response

Organization

No response

Declaration

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

[kineticjs]

Hi @gnseo,

Thank you for reaching out. While it may seem like a natural expectation for the change event to carry the selected item in its detail, the current behavior is intentional.

By design, the change event is modeled after the native HTML <input> change event.

Why this makes sense:
ComboBox allows free-text input — the user can type any value, not just select from the list. When change fires, there may be no matching item at all, so event.detail.item would be misleading (sometimes present, sometimes null).

selection-change is the dedicated event for item selection — it fires specifically when the selected item changes, and provides event.detail.item (or null when selection is cleared). This is the right event for reacting to item picks.

[gnseo]

@kineticjs Thank you for your reply.
I think if the "change" event is triggered when user selects from the list, then it would be better to provide which item is selected too.
If so, we could determine if the "change" event was triggered by selecting from the list or entering free text by checking if "event.detail.item" was null.
It's also supported in OpenUI5 by the way.

Could you please re-consider this?

Regards.

[Vonahz]

Hi @gnseo ,

Thank you for the feedback. The separation between change and selection-change is intentional and follows web standards patterns:

• change aligns with native HTML form element behavior, signaling value finalization for form validation and submission
• selection-change provides item-specific context for UI interactions

This design:
Follows native and patterns where change events don't include interaction details Allows clear separation: use change for form logic, selection-change for selection tracking Integrates better with web standards and form libraries While OpenUI5 may combine these concepts, Web Components prioritize web standards alignment over framework-specific APIs. For use cases requiring both events, you can listen to both separately.

[github-actions]

This issue has been closed. To reopen, just leave a comment!

[gnseo]

Hi, @Vonahz .

I just found that in 0.20.0 version, you've just added new properties - selectedValue for ComboBox, value for ComboBoxItem.
I think I can solve my problem using those new properties.

I'll give a try later.

Regards.

[Vonahz]

Great!

I'll go ahead and close this now. If you encounter any other issues or have additional questions, please feel free to open a new issue.

Regards.