Skip to content

[ui5-combobox] Change event is not fired as documented on ui5-combobox #5432

@ixiler

Description

@ixiler

Bug Description

All the descriptions bellow are about ui5-combobox component
The change event doesn't fire when the value in the input matches a ui5-cb-item text attribute exactly. In such case the event is not fired when the ui5-cb-item is clicked, when the Enter button is pressed and when the input is focused out.

Expected Behavior

The change event to fire as per the documentation description "Fired when the input operation has finished by pressing Enter, focusout or an item is selected.".
A temporary workaround would be appreciated as well, since using selection-change events fires before the user interaction is finished (pressing enter, clicking on a ui5-cb-item or focusing out). The Enter press and focus out already have workarounds on our end, but couldn't catch the ui5-cb-item event.

Steps to Reproduce

  1. Go to the sandbox
  2. Enter Item1 into the combo box
  3. Press Enter
  4. Observe that the event is not fired, the Selected value is not updated in the designated span and no log is present in the console.
  5. The Item1 value should still be present in the input. Open the dropdown.
  6. Click on Item1
  7. Observe that the event is not fired, the Selected value is not updated in the designated span and no log is present in the console.
  8. Focus the input
  9. Focus out the input
  10. Observe that the event is not fired, the Selected value is not updated in the designated span and no log is present in the console.

Isolated Example

The sandbox provided is a simple one: There is a single combobox with 3 items and a span above it that is changed by the events fired by the change event. Also the subscription to the change event logs the received value to the console.
sandbox

Context

  • UI5 Web Components version: {1.4.0}
  • OS/Platform: {any}
  • Browser: {any}
  • Affected component: {ui5-combobox}

Log Output / Stack Trace / Screenshots

Priority

  • Low
  • Medium
  • High
  • Very High

The priority indicates the severity of the issue. To set the appropriate priority consider the following criteria:

  • Breaks entire application or system - High or Very High
  • Accessibility issue - Medium or High
  • Functional issue - Medium or High
  • Visual issue - Low or Medium

Note: The priority might be re-evaluated by the issue processor.

Stakeholder Info (if applicable)

  • Organization: {SAP}
  • Unit: {Automation Pilot}
  • Business impact: {Customers already complain that the data they enter is not updated on form submit}

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Completed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions