fix(ui5-multi-combobox): fix token deletion when click event is lost due to re-render#13530
Merged
Conversation
Collaborator
|
🧹 Preview deployment cleaned up: https://pr-13530--ui5-webcomponents.netlify.app |
…multicombobox_bug
aleksandar-terziev
approved these changes
May 21, 2026
Collaborator
|
🎉 This PR is included in version v2.23.0-rc.0 🎉 The release is available on v2.23.0-rc.0 Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version v2.23.0 🎉 The release is available on v2.23.0 Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #13514
Token deletion would fail intermittently when clicking the delete icon
because the mousedown event set toBeDeleted=true, which could trigger
a re-render that replaced the delete icon DOM element before the click
event fired, causing the click event to be lost and preventing deletion.
This was most easily reproduced when tokens were collapsed/overflown,
but could happen in various scenarios where DOM updates occurred between
mousedown and click events.