fix: Limit calculation bug when dragging and resizing #397
Conversation
This file contains 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
…nd right mouse buttons clicked simultaneously
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
Phenomenon: When both left and right mouse buttons are pressed simultaneously to drag or resize, the component becomes "stuck" and can only be restored by refreshing the page.
Cause: When the left mouse button is clicked, it indicates dragging or resizing. If the right mouse button is accidentally pressed at this time, the mousedown event triggers the ”deselect“ function and resets the mouse state in the DOM. This can lead to incorrect internal calculations resulting in NaN.
Solution: Both drag and resize events share a common feature of triggering a mouse click event. A local variable can be created as a "lock." This "lock" is then released after the mouseup event occurs.