Fix unexpected modelValue emit if no checkbox value is set #18552
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 #18550
When using a checkbox with a custom value in
select-multiple-checkbox
that does not yet have a value set the checkbox component previously emitted anupdate:modelValue
event withfalse
as payload, even though it was used with an arraymodelValue
because of the else branch in L106.I also included a small usability fix that prevents focusing (by clicking) the input from toggling the checkbox.