fix(splitter): minSize behavior during fast mouse movement #7099
+29
−12
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.
Fix #7001
The issue was due to premature validation - the user would move the mouse too fast skipping the values close to the minSize and we would evaluate that as invalid change (and it was), but we did not update the elements with the minimum size.
That is why when the minSize was set to 20 it could end up being anything above 20 even though the mouse was way beyond the min size limit.