-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MultiInput: change event wouldn't be fired when typed value is as same as the first token #6262
Comments
Hi @echowwww , Are you reproducing this on https://sap.github.io/ui5-webcomponents/playground/components/MultiInput/ , I set a breakpoint and see that the "change" event is fired but the logic for keeping unique tokens only executes, as shown in the screenshot below: Please comment if you are testing on a different sample. |
Yes, i use this on https://sap.github.io/ui5-webcomponents/playground/components/MultiInput/ , |
Hi @SAP/ui5-webcomponents-topic-rl, Can you please check this issue with handling of duplicate input texts in ui5-multiinput: To reproduce:
The issue seems to be related to the logic in the _handleChange function of ui5-input, which fires the "change" event only if a precondition with the previously entered value is in place. |
when the user types something then hits enter the value is set to the input field value. If the user change the value in the change handler, internals used to be not updated correctly and prevented correct future firing of the change event. FIXES: #6262
Bug Description
If the second input has the same value as the first input, change event wouldn't be fired and user cannot press enter.
Expected Behavior
change event should be fired when user press enter or focus out the input field. In change event listener, user can then check for duplicated input or perform other actions.
Steps to Reproduce
Context
Log Output / Stack Trace / Screenshots
Priority
The priority indicates the severity of the issue. To set the appropriate priority consider the following criteria:
Note: The priority might be re-evaluated by the issue processor.
The text was updated successfully, but these errors were encountered: